fix: make Cloud DNS NS delegation idempotent#1932
Merged
Merged
Conversation
RealHarshThakur
approved these changes
Jul 16, 2026
im-Amitto
added
the
promote-all
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-up to #1929 and #1931. The GCP delegation path used additions-only, so retries and reprovisions failed with 409 alreadyExists. Cloud DNS has no native upsert, so look up the existing NS record set and replace it (delete + add in one change), no-op when unchanged. Matches the Route53 path's upsert behavior.