-
Notifications
You must be signed in to change notification settings - Fork 548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DO NOT Merge: Add commit confirmed plus commit message support #550
Conversation
Resubmitted due to some merge conflicts...see additional notes here: #544 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ktbyers is this ready (at least for IOS)? Junos and IOS-XR support both confirmed and message, I can continue from here if that's fine.
"""Commit configuration.""" | ||
if confirmed is not None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Junos supports commit confirmed (and message).
@@ -145,7 +145,10 @@ def compare_config(self): | |||
else: | |||
return self.device.compare_config().strip() | |||
|
|||
def commit_config(self): | |||
def commit_config(self, confirmed=None, message=None): | |||
if confirmed is not None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IOS-XR too (also message).
@mirceaulinic Cisco IOS should be ready. I tested that when I implemented it. |
@mirceaulinic Let me know when you add this into other platforms and I will regression test it in my lab environment. We should also regression test it when it gets merged into develop branch (which I should be able to do also). |
@@ -178,12 +178,16 @@ def compare_config(self): | |||
""" | |||
raise NotImplementedError | |||
|
|||
def commit_config(self): | |||
def commit_config(self, confirmed=None, message=None): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should document what "confirmed" is supposed to be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also really think we shouldn't name this variable confirmed
. It is a terrible name; revert_in
or timer
are way better names.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
confirmed
is logical and is the most widely adopted name for this function. Basically saying you have to confirm
this commit in how many minutes.
I think we will probably just add more confusion by naming it something else.
But agreed...it needs documented.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on revert_in
, describes the intent better. confirmed
nomenclature maybe better known by network engineers, but I wouldn't cater to them exclusively with this library, you may have engineers without that background.
I think this whole functionality requires two extra methods:
|
Added two methods per @dbarrosop comment (although I changed the name of one of them). Implemented and tested them on Cisco IOS. |
Awesome! :) |
@dbarrosop @mirceaulinic Did some more research and review (which also helped me remember past research):
|
We need to confirm 5. @mirceaulinic is that something you can look into? |
Closing...don't think it makes sense to keep this PR open any longer. |
No description provided.