Resource type-level component order

Open
#199 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
azure, csharp
Domain
cloud

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AzureNamingTool

All issues in Azure/AzureNamingTool

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.