[Promoted to epic&6814] Project create should ensure a corresponding ProjectNamespace record is created
Before we can start populating existing projects with a corresponding ProjectNamespace we need to ensure that all new projects create its corresponding ProjectNamespace record. This will allow us to run the migration for existing projects once, without worrying about backfilling data for new projects.
Also having creating a ProjectNamespace record on project creation first, will allow us to feature flag it and monitor any unaccounted for behaviour before we add the record for all projects.
Tasks
-
Handle project and namespace name validations inconsistencies in order to be able to add correspinding ProjectNamespace for each project -
Add namespaces filtering to exclude ProjectNamespaces
when fetchingGroup
s -
Introduce migrations to make the path unique between Namespace and ProjectNamespace -
make sure that the project namespace is auto-created also on project import (no extra work should be needed if we handle project namespace creation as an AR callback
Edited by Alexandru Croitor