Skip to content

Resource type-level component order #199

@argiesen

Description

@argiesen

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions