Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AzNamingTool - Feature Request: Component as optional globally #102

Closed
hmizael opened this issue Oct 19, 2022 · 3 comments
Closed

AzNamingTool - Feature Request: Component as optional globally #102

hmizael opened this issue Oct 19, 2022 · 3 comments

Comments

@hmizael
Copy link

hmizael commented Oct 19, 2022

I would like to suggest the feature of being able to configure a component as optional globally, as it is already possible to activate or deactivate it. Both for native components and for custom components.

Thank you very much!

@hmizael hmizael changed the title Feature Request: Component as optional globally AzNamingTool - Feature Request: Component as optional globally Oct 19, 2022
@BryanSoltis
Copy link
Collaborator

Hi @hmizael,

Thank you for your suggestions. That would be a valuable feature to allow you to not have to edit every resource type to make a component optional. WE will add that to our backlog.

  • Bryan

@BryanSoltis
Copy link
Collaborator

Hi @hmizael,

I wanted to let you know we have continued to work on this feature and it will be included in the next release (v.2.4.0) hopefully in the next few weeks. The site will allow you to mark a component as optional for every resource type.

image

We will post an announcement once the change is published. Thank you for the great suggestion!

  • Bryan

@hmizael
Copy link
Author

hmizael commented Dec 21, 2022

Thank you so Much for that!
Eagerly awaiting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants