-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Private DNS Zones Bug (#695) #891
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM , should we add an example specifically for multi-region to make it clear how to add region-aware private dns zones ?
@sebassem is this not already in the hub spoke multi-region, where i call the DNS zones twice with a different location. I actually plan on adding the feature to my AVM modules to make it a simpler toggle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and you're good with the multi-region adjustments you made from my point of view.
I also tested the Accelerator, and all looks good. Thanks much!
/azp run validateazcloud |
Azure Pipelines successfully started running 1 pipeline(s). |
Overview/Summary
This PR Fixes the Private DNS Zones Bug #695
Related Issues/Work Items
Fixes #695
This PR fixes/adds/changes/removes
Breaking Changes
A number of breaking changes
Draft Release Notes
The local private DNS zones modules (
privateDnsZones.bicep
) has been replaced in the networking related modules in this repo with the AVM Pattern module ofavm/ptn/network/private-link-private-dns-zones
to resolve bug #695.This has meant some breaking changes to each of the networking modules that are detailed below.
privateDnsZones.bicep
v0.20.0
and replaced with the AVM Pattern Module ofavm/ptn/network/private-link-private-dns-zones
. Please use this module going forward.hubNetworking.bicep
&hubNetworking-multiRegion.bicep
parPrivateDnsZones
default value changed to an empty array ([]
)parPrivateDnsZoneAutoMergeAzureBackupZone
removed from moduleparVirtualNetworkResourceIdsToLinkTo
added to module, you can prefer to use this parameter instead ofparVirtualNetworkIdToLink
&parVirtualNetworkIdToLinkFailover
if you wish (they are automatically all merged together by the module anyway)outPrivateDnsZones
has changedFrom:
To:
vwanConnectivity.bicep
parPrivateDnsZones
default value changed to an empty array ([]
)parVirtualNetworkIdToLink
&parVirtualNetworkIdToLinkFailover
removed from module and replaced withparVirtualNetworkResourceIdsToLinkTo
outPrivateDnsZones
has changedFrom:
To:
Testing Evidence
As part of this Pull Request I have
.bicep
file/s I am adding/editing are using the latest API version possiblemain
branch