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
Currently, calling rollback() on NXOS does nothing unless napalm is aware of making changes. However, in some cases it makes sense to call rollback() in a new napalm session.
Proposed behavior is that rollback() will become agnostic to any changes napalm is aware of, and will have the net effect of reverting to the most recent state. For platforms with a native rollback feature, this will revert to the most recent snapshot. Platforms that don't, such as IOS, will attempt to revert to the rollback state that napalm created in a previous session. If such a rollback state does not exist, an exception will raise.
The text was updated successfully, but these errors were encountered:
decoupca
added a commit
to decoupca/napalm
that referenced
this issue
Sep 6, 2023
Based on this discussion.
Currently, calling
rollback()
on NXOS does nothing unless napalm is aware of making changes. However, in some cases it makes sense to callrollback()
in a new napalm session.Proposed behavior is that
rollback()
will become agnostic to any changes napalm is aware of, and will have the net effect of reverting to the most recent state. For platforms with a native rollback feature, this will revert to the most recent snapshot. Platforms that don't, such as IOS, will attempt to revert to the rollback state that napalm created in a previous session. If such a rollback state does not exist, an exception will raise.The text was updated successfully, but these errors were encountered: