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
On your point 1, I think we should just add an attribute to the napalm object where we track the file_prompt_quiet state. Once we change this once, then we set that flag to True. Then in the napalm close() method, if that file_prompt_quiet flag has been set to True, we re-set it back to no file prompt quiet.
Basically since we are making a configuration change to the device, we should only do it if we need to (i.e. we shouldn't do it in open() as then you would be making this config change even for getter operations). But if we do it for config() operations and then just track the state so we only do it once, that would be a big improvement.
I'll give it a go.
The text was updated successfully, but these errors were encountered:
vladola
changed the title
[Enhancement] Enable file prompt quiet only once at the beginning of a configuration method
[Enhancement] Enable file prompt quiet only once at the beginning when configuration occurs for cisco_ios
Dec 21, 2018
Essentially what @ktbyers described in this comment of issue #879
I'll give it a go.
The text was updated successfully, but these errors were encountered: