-
Notifications
You must be signed in to change notification settings - Fork 512
fix: Update deployment name composition #6314
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
Merged
jtracey93
merged 5 commits into
main
from
users/jtracey93/fix/deployment-name-usage-for-alz
Dec 6, 2025
Merged
fix: Update deployment name composition #6314
jtracey93
merged 5 commits into
main
from
users/jtracey93/fix/deployment-name-usage-for-alz
Dec 6, 2025
+69
−49
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
- Removed usage of `deployment().name` in module names to enhance performance during redeploys and when used in deployment stacks. - Updated module names to use `managementGroup().name` and other parameters for uniqueness. - No functional changes to the module.
- Refactor deployment names for subscription and resource group policy assignments to include management group name for uniqueness. - Ensure compliance with naming conventions and improve clarity in deployment identifiers. - Module path: avm/ptn/authorization/policy-assignment
- Refactored deployment name generation to eliminate usage of `deployment().name` for improved performance and reduced deployment count. - Updated module names in main.bicep and main.json for management group, subscription, and resource group role assignments. - No functional changes to the module.
- Updated serviceShort parameter values in multiple test files to ensure uniqueness and avoid conflicts. - Affected files include role assignments for management group, resource group, and subscription scopes.
- Corrected serviceShort parameter values in multiple test files for role assignment. - Ensured consistency in naming conventions across management group, resource group, and subscription scopes. - Updated files: mg.defaults, mg.max, rg.default, rg.max, sub.default, sub.max.
jaredfholgate
approved these changes
Dec 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Needs: Core Team 🧞
This item needs the AVM Core Team to review it
Needs: Triage 🔍
Maintainers need to triage still
Type: AVM 🅰️ ✌️ Ⓜ️
This is an AVM related issue
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
deployment().namein module names to enhance performance during redeploys and when used in deployment stacks.deployment().namewith Deployment Stacks in large deployments increases chances of hitting 800 deployments at a scope limit bicep#18621 for infoPipeline Reference
Type of Change
version.json:version.json.version.json.Checklist
Set-AVMModulelocally to generate the supporting module files.