fix: DevOps CI/CD agents pattern module DNS properties were not used and added dnsIsDeployedByPolicy property#5944
Conversation
- Added optional parameter 'dnsIsDeployedByPolicy' to control DNS deployment by policy. - Updated private DNS zone group logic to utilize the new parameter.
- Introduced a new parameter `dnsIsDeployedByPolicy` to indicate if the DNS configuration is deployed by policy. - Updated README.md to document the new parameter. - Modified main.json to include the new parameter in the parameters section.
- Updated API version for private DNS zone and container registry modules. - Adjusted references to outputs for new version compatibility. - Updated managed environment and job module versions for consistency.
|
Important The "Needs: Triage 🔍" label must be removed once the triage process is complete! Tip For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation. |
|
Important If this is a module-related PR, being submitted by the sole owner of the module, the AVM core team must review and approve it (as module owners can't approve their own PRs). To indicate this PR needs the core team''s attention, apply the "Needs: Core Team 🧞" label! The core team will only review and approve PRs that have this label applied! |
dnsIsDeployedByPolicy property
dnsIsDeployedByPolicy propertydnsIsDeployedByPolicy property
|
@johnlokerse can you resolve the merge conflicts |
|
@jtracey93 Done, but I have some issues with generating the README via
|
Regarding this @johnlokerse, please run the script with the corresponding skips. For example: Maybe it's time to flip this skip-switch parameter on its head. |
That works! Pushed changes. |
|
Closing in favor of #7030 @johnlokerse you'll remain the author of the changes as I just rebased the PR to resolve the conflicts. |


Description
Ran into some DNS issues when bringing your own DNS setup and when using DINE policies. This pull request removes
privateDnsZoneGroupNameandprivateDnsZoneResourceIdsin moduleacr. These properties were not used. Updated them to the correct properties as defined in the UDT. Additionally, added the parameterdnsIsDeployedByPolicyto be able to skip the configuration of privateDnsZoneGroups.Updated modules to the latest version.
Pipeline Reference
Do you have an environment set up @sebassem so this change can be tested?
Type of Change
version.json:version.json.version.json.Checklist
Set-AVMModulelocally to generate the supporting module files.