CLOUDP-330314: Disallow project/deployment renaming #2441
Merged
+118
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tvdw-mongodb
force-pushed
the
no-rename-project
branch
from
797b9ea to
cf5ecc0
Compare
tvdw-mongodb
changed the title
tvdw-mongodb
force-pushed
the
no-rename-project
branch
from
cf5ecc0 to
9136753
Compare
tvdw-mongodb
changed the title
tvdw-mongodb
force-pushed
the
no-rename-project
branch
from
9136753 to
5f51e17
Compare
When a project is renamed in Kube, the operator will create a new project and leave the original intact, while other resources (such as AtlasDeployment) still track the original clusters in the old project. This leads to bad situations that are difficult to clean up, in particular via the operator. Similarly, when a deployment is renamed in Kube a new deployment is created in Atlas, with the old one left running. Since this is almost definitely not what the user wanted, let's ensure that name changes here are also forbidden.
tvdw-mongodb
force-pushed
the
no-rename-project
branch
from
5f51e17 to
bd95e7c
Compare
josvazg
approved these changes
Jul 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a project is renamed in Kube, the operator will create a new
project and leave the original intact, while other resources (such as
AtlasDeployment) still track the original clusters in the old project.
This leads to bad situations that are difficult to clean up, in
particular via the operator.
Similarly, when a deployment is renamed in Kube a new deployment is
created in Atlas, with the old one left running. Since this is almost
definitely not what the user wanted, let's ensure that name changes here
are also forbidden.
Checklist