Merged
Conversation
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.
This pull request updates Azure region short name mappings in both the main ARM template and the private DNS zones policy set definition. The main focus is on adding support for new Azure regions, updating existing mappings, and ensuring consistency across the codebase. Additionally, the policy set definition version is incremented to reflect these changes.
Azure region short name mapping updates:
centraluseuap,eastus2euap,eastus3,indiasouthcentral,israelnorthwest,jioindiacentral,jioindiawest,malaysiasouth,northeastus5,southcentralus2,southeastus,southeastus3,southeastus5,southwestus, andswedensouthin botheslzArm.jsonandDeploy-Private-DNS-Zones.jsonfor improved regional coverage. [1] [2] [3] [4]austriaeast,belgiumcentral,denmarkeast,indonesiacentral,taiwannorthwest, and several US government and DoD regions. [1] [2]Consistency and cleanup:
azBackupGeoCodesvariable ineslzArm.jsonto prevent redundancy.Versioning:
Deploy-Private-DNS-Zones.jsonpolicy set definition from2.4.0to2.5.0to reflect the new region support and mapping updates.Other:
eslzArm.json.