You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When you deploy MLZ using deploy.sh, it creates resource groups for the terraform state as well as for the actual landing zone tiers. The names that are generated are very similar and could be confusing to users, especially when scanning the list of resource groups.
Describe the solution you'd like
I think making the naming a bit more verbose would clarify issues. Instead of the current naming, maybe spell out 'terraform' or 'tfstate' in the RG, such as rg-terraform-tier1-mlz-12345678 or rg-tfstate-tier1-mlz12345678
Describe alternatives you've considered
Considered tagging, but the default behavior of the portal isn't to show tags or group by tags, so that would take more steps and Azure knowledge to delineate the different groups of RGs.
Additional context
See above
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When you deploy MLZ using
deploy.sh
, it creates resource groups for the terraform state as well as for the actual landing zone tiers. The names that are generated are very similar and could be confusing to users, especially when scanning the list of resource groups.Describe the solution you'd like
I think making the naming a bit more verbose would clarify issues. Instead of the current naming, maybe spell out 'terraform' or 'tfstate' in the RG, such as
rg-terraform-tier1-mlz-12345678
orrg-tfstate-tier1-mlz12345678
Describe alternatives you've considered
Considered tagging, but the default behavior of the portal isn't to show tags or group by tags, so that would take more steps and Azure knowledge to delineate the different groups of RGs.
Additional context
See above
The text was updated successfully, but these errors were encountered: