Update azure resource naming conventions again and possibly make them configurable
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Possibly make this configurable via the workload spec?
Basically, we need to have the parts be interchangeable.
Default something like:
-<business unit/dept>-<workload/app/project>---
Example: rsg-ptd-customer1-dev-usw1-01
(Or put ptd in a tag or something, owner: ptd)
And then for each workload possibly we allow the customer to dictate the order of all of those components. This will at least get us close to most naming policies I think.
https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming
https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations (for more comprehensive list: https://github.com/mspnp/AzureNamingTool/blob/01a8d2d94bc0bd76277b4265db19b93c1e69a194/src/repository/resourcetypes.json)
Contributor guide
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 by reviewing the workload spec, which the issue identifies as the possible configuration entry point, and compare the linked Azure naming guidance. Define the default component order and determine how workloads can make those components interchangeable. Done means the naming policy supports the stated default and workload-specific ordering, with the Azure naming requirements addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100