Feature Request: Update naimng to confirm with CAF naming Standards

ashley-kainos commented 1 year ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Naming of resources is not 100% inline with the CAF naming standards, it would be good if they were to follow as in link below https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming

An example is management Groups should be named mg- currently they deploy -

Is your feature request related to a problem?

Describe the solution you'd like

All resources to be deployed using the naming convention in link below so it creates a standard naming convention when talking to client and customers as it currently conflicts

Additional context

matt-FFFFFF commented 1 year ago

Hi @ashley-kainos

We plan to address this in the next major version. This is likely to be a breaking change.

matt-FFFFFF commented 1 year ago

also #292

ppodevlabs commented 1 year ago

any ETA for the next major?

matt-FFFFFF commented 1 year ago

Nothing to share at the moment. We are working on the approach for v.next and will publish when we have decided.

davidmonk-cbts commented 7 months ago

This is rather embarrassing when you present deployment of a standard landing zone to the customer and MS reference architectures and practices, then you get to the actual deployment of their landing zone using the MS recommended practices, and the platform landing zone naming does not comply with the recommended naming convention. This has been talked about for almost 2 years. It was tagged for the next major version 2 major versions ago. Will there ever be any movement on this?

kardiojack commented 7 months ago

Is there any way to align the names of management groups with MS recommended best practices? The module seems to have the management group names hardcoded into the logic of the local variables and json templates.

Not having proper naming makes this module a Catch 22. I want to use a Microsoft module to avoid making a bespoke Terraform setup but the design of this module pushes me towards making a bespoke setup...

Azure / terraform-azurerm-caf-enterprise-scale