You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
hmizael
changed the title
Feature Request: Component as optional globally
AzNamingTool - Feature Request: Component as optional globally
Oct 19, 2022
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.
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.
We will post an announcement once the change is published. Thank you for the great suggestion!
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!
The text was updated successfully, but these errors were encountered: