[BUG] - project name validation

[pmeier]

Describe the bug

During nebari init --guided-init we are checking the project name in two places:

1. When putting it in with

   nebari/nebari/schema.py

   Line 519 in 8bd56f9

   def project_name_convention(value: typing.Any, values):

2. While rendering the config with

   nebari/nebari/initialize.py

   Lines 360 to 363 in 8bd56f9

   	if not re.match(namestr_regex, namespace):
   	raise ValueError(
   	"namespace should contain only letters and hyphens/underscores (but not at the start or end)"
   	)

Unfortunately, these methods diverge:

1. nebari/nebari/schema.py

   Lines 520 to 529 in 8bd56f9

   	convention = """
   	There are some project naming conventions which need to be followed.
   	First, ensure your name is compatible with the specific one for
   	your chosen Cloud provider. In addition, the project name should also obey the following
   	format requirements:
   	- Letters from A to Z (upper and lower case) and numbers;
   	- Maximum accepted length of the name string is 16 characters.
   	- If using AWS: names should not start with the string "aws";
   	- If using Azure: names should not contain "-".
   	"""

2. nebari/nebari/utils.py

   Line 41 in 8bd56f9

   namestr_regex = r"^[A-Za-z][A-Za-z\-_]*[A-Za-z]$"

Some differences (not exhaustive):

• 1. allows numbers while 2. doesn't
• 1. allows a maximum of 16 characters, while 2. allows arbitrary lengths
• 1. has extra rules depending on the cloud provider, while 2. does not
• 2. doesn't allow underscores or hyphens, while 1. does (it is not mentioned in the docstring, but it does)

Expected behavior

If a project name passes the initial validation, there should be no errors down the line.

OS and architecture in which you are running Nebari

How to Reproduce the problem?

Command output

No response

Versions and dependencies used.

No response

Compute environment

None

Integrations

No response

Anything else?

No response

[pavithraes]

@iameskild - Potential solution could be to check project name separately for each cloud provider. This is also blocked by the extension mechanism work.

[kenafoster]

I've created two related issues around project naming conventions

#2001
#2002