Reimport Tenant with already used identifier
M
Mohammad Javad Kazemi
So often happens that the OpenShift team want to delete a project but being able to use the same ID to create a new one.
Currently the only way is to create a support ticket and getting it manually unblocked from the backend.
On the technical part, we are aware of the downsides so we make sure to:
- Reuse the ID only within the same Workspace
- Remove and clean-up all the related resources
Felix
Tenants for which an identifier should be reused will not be shown again "unmanaged tenants" again, even after the support ticket for reusing is closed. This does not prevent an adoption via API.
Jelle den Burger
Merged in a post:
Reimport tenant
Felix
At the moment, meshStack blocks all attempts to import a tenant that was previously deleted.
The need to import a previously managed tenant again arises for example when:
- The tenant was deleted accidentally.
- The tenant should be moved to a different landing zone https://meshcloud.canny.io/feature-requests/p/move-tenant-to-different-landing-zone
- The tenant should be moved to a different project https://meshcloud.canny.io/feature-requests/p/move-projects-between-workspaces
Workaround: meshcloud support unblocks the tenant manually.