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
Allow for permanent / sticky manual config plans.
As of today, a manual config plan has to be created per each individual device configuration change.
Modified list view for config plans - this should introduce tabs for config plans with different statuses, making UI navigation much easier and faster.
A "workflow" like experience would be added. Proposed tabs could be similar to statuses :
Pending Approval
Pending Deployment
Running
Completed
Permanent
Use Case
Allow network operators to re-use config-plans in a "job" manner.
Common use cases could be BGP peering flap, interface flap, where a pre-defined scenario is saved permanently.
As of today, this is not possible because of config_deployment method :
if config_plan_qs.filter(status__name="Completed").exists():
error_msg = "`E3026:` Cannot deploy configuration(s). One or more config plans are already completed."
logger.error(error_msg)
raise NornirNautobotException(error_msg)
Solution
Introduce a bool flag on ConfigPlan object that would allow for re-deployments.
Modify list view for config plans.
The text was updated successfully, but these errors were encountered:
mzbroch
changed the title
Config plan re-deployments
Config plan list view and config plan re-deployments
May 14, 2024
Environment
Proposed Functionality
Allow for permanent / sticky manual config plans.
As of today, a manual config plan has to be created per each individual device configuration change.
Modified list view for config plans - this should introduce tabs for config plans with different statuses, making UI navigation much easier and faster.
A "workflow" like experience would be added. Proposed tabs could be similar to statuses :
Use Case
Allow network operators to re-use config-plans in a "job" manner.
Common use cases could be BGP peering flap, interface flap, where a pre-defined scenario is saved permanently.
As of today, this is not possible because of
config_deployment
method :Solution
Introduce a bool flag on ConfigPlan object that would allow for re-deployments.
Modify list view for config plans.
The text was updated successfully, but these errors were encountered: