Skip to content
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

Naming Azure resources rule feedback #3239

Open
bradystroud opened this issue May 19, 2022 · 3 comments
Open

Naming Azure resources rule feedback #3239

bradystroud opened this issue May 19, 2022 · 3 comments

Comments

@bradystroud
Copy link
Member

bradystroud commented May 19, 2022

Cc: @adamcogan @pierssinclairssw @matt-goldman @wicksipedia @brydeno

Hi @lukecookssw,

https://www.ssw.com.au/rules/azure-naming-resources

This naming convention wont work in some scenarios. There is a plan for the exceptions section but it doesn't actually explain how to plan for exceptions.

The rule should suggest how to handle exceptions, or not suggest a naming convention at all.
Not suggesting a naming convention would make this rule easier to maintain.

  1. If you agree, update the rule to not suggest a naming convention
@wicksipedia
Copy link
Member

Hey @bradystroud
Some of us had a discussion last night about aligning more with https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming which should make things easier to maintain.

Hey @lukecookssw maybe the exception for storage accounts should be called out since it is a common one

@tiagov8
Copy link
Member

tiagov8 commented Dec 8, 2022

Hey @bradystroud

Could this issue be closed?

@bradystroud
Copy link
Member Author

bradystroud commented Dec 16, 2022

Hey @tiagov8

No - still an issue
I would prefer this rule to reccomend following Microsoft's reccomendations rather than our own format that we will need to maintain as per @wicksipedia 's suggestion

This probably wont be actioned but I'll keep the issue here as a 'for the record'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants