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
This lacks the flexibility some multi-vendor environments (specifically with a mix of CLI and controller based) platforms need. It would be great to move these ENABLE features into each GC setting.
Proposed Functionality
Remove all the conditional logic throughout the app that is based on ENABLE features options. This moves the app more in line with what all other apps, core do today, still show the object, nav in UI, if you don't use them then you don't use them. (furthermore, if users want this they can now accomplish it view saved views)
Add toggle options on the golden config setting itself for each of the ENABLE feature options.
Have a default boolean of sorts that defaults the default GC setting to what is in plugin_config.
To provide an example of the new GC settings view.
Use Case
All backup, intended, compliance on a GC setting but don't allow config plans or deploys (since a controller must do it in those cases)
I don't use GC for backups, but a custom job pulls the backup data into nautobot, I still want the UI views, and nav menu to show models that I may use in a backup "post processing" of sorts.
The text was updated successfully, but these errors were encountered:
Environment
Today the app is configured to hide views, menu items, etc. based on the global config settings e.g.
This lacks the flexibility some multi-vendor environments (specifically with a mix of CLI and controller based) platforms need. It would be great to move these ENABLE features into each GC setting.
Proposed Functionality
To provide an example of the new GC settings view.
Use Case
The text was updated successfully, but these errors were encountered: