Resource type-level component order
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the global component-order configuration and the resource-type configuration, then trace how names are generated for key vaults and event hubs. Done means an individual resource type can override the global order while existing global ordering remains the default.
Written by the indexing model from the issue text.
Description
Tool version
v5.0.2
Is your feature request related to a problem? Please describe.
I have a large customer whose naming convention starts with a number for their business unit IDs. However, there are resources that do not support starting with a number such as key vaults, event hubs, and a few others. For those resources they typically put the resource type short name there.
Describe the solution you'd like
I would like the ability to override the global component order at a resource type level to allow for these scenarios.
Describe alternatives you've considered
I've considered adding an optional free form text component at the top of the component order for those resources.
Additional context
Nothing to add.
- Dominant language
- C#
- Stars
- 604
- Forks
- 1.3k
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 3
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.
More from Azure/AzureNamingTool
-
missing data
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
Azure/AzureNamingTool#183 · 3 reactions ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Azure/AzureNamingTool#162 ·
-
missing data
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
Azure/AzureNamingTool#161 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
Azure/AzureNamingTool#160 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Azure/AzureNamingTool#159 ·
All issues in Azure/AzureNamingTool
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·