Repository navigation
Allow the Front Door profile and DNS zone to live in other subscriptions - #30
Merged
Merged
Conversation
Shared edge and DNS resources often sit in their own subscriptions, and the template could only reach a profile and zone in DevBrain's own subscription. - Add optional FRONT_DOOR_SUBSCRIPTION_ID and DNS_ZONE_SUBSCRIPTION_ID azd values (frontDoorSubscriptionId, dnsZoneSubscriptionId). The Front Door subscription defaults to DevBrain's, and the DNS zone's defaults to the Front Door profile's, matching how the resource groups already default. - Document the cross-subscription values and the cutover steps for moving an existing deployment behind Front Door. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Summary
The Front Door option from #27 only reached a profile and DNS zone in DevBrain's own subscription. Shared edge and DNS resources often live in their own subscriptions, so this adds two optional azd values:
FRONT_DOOR_SUBSCRIPTION_IDfrontDoorSubscriptionIdDNS_ZONE_SUBSCRIPTION_IDdnsZoneSubscriptionIdThe defaults mirror how the resource-group values already cascade, so existing deployments and single-subscription setups are unchanged.
The README also gains a short cutover note for moving an existing deployment behind Front Door:
DEVBRAIN_MCP_URL.Validation
az bicep build --file infra/main.bicepsucceeds.az deployment group what-ifagainst an existing deployment whose Front Door profile and DNS zone each sit in a different subscription. The new Front Door resources, the WAF policy and both DNS records resolve into the correct subscription and resource group. The profile's existing endpoint and WAF policy show asIgnore(untouched).🤖 Generated with Claude Code