feat(custom-domain): configure relay service attachment#62
Merged
Conversation
Co-authored-by: Codex <noreply@openai.com>
nandajavarma
marked this pull request as ready for review
July 20, 2026 17:20
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
1 participant
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.
Description
Allow the custom-domain client module to target a non-production PSC service attachment while preserving the existing production attachment as the default.
This lets staging deployments reference the shared module directly instead of copying it.
Compatibility
Existing callers are unchanged because
service_attachment_uridefaults to the current production service attachment.Verification
terraform fmt -check -recursive .terraform init -backend=falseterraform validateterraform-docsversionDocumentation
The module README and example variables document the optional override.