Update ProjectNamespace name validation
When we create (or backfill) a project namespace for each project, there may be a validation issue for some edge case project names because there are differences in validation restrictions for projects and namespaces:
- project name can be only single char, namespaces must have at least two chars (we have currently ~33k of single char projects), introduced in #225214 (closed)
- project name can end with
.
, namespace can not (we have ~2.6k projects ending with.
)
To avoid validation errors (when project namespace with the same name is created), we have to either:
- make project validation stricter (to align with namespace validation) and rename existing projects - this is probably not feasible w/o a deprecation period
- allow to create project namespace with single char names or ending with
.
- this may be a solution for now, we would allow single char or.
only for project namespaces, so nothing would change from user point of view
Proposal
- Keep validations for Projects the same for the initial release
- Tackle parity for validation in a separate issue #341764 (closed)
Related to #340495 (closed).
Edited by Alexandru Croitor