SSWConsulting / SSWConsulting/SSW.Rules.Content
Naming Azure resources rule feedback
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 62
- Forks
- 196
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 112
Description
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.
- If you agree, update the rule to not suggest a naming convention
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Azure resource naming rule at https://www.ssw.com.au/rules/azure-naming-resources and locate its source in the repository. Review the existing exceptions section and the requested alternative, then update the rule so its treatment of naming conventions and exceptions matches the agreed direction. Done means the rule no longer makes an unworkable recommendation or clearly explains how to handle exceptions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100