-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Bug fixes in Junos-related components #55824
Conversation
Fixes multiple bugs found by test team
Fixes multiple PRs raise by test team
Used pre-commit tools and also done suggested changes like a single quote to double. |
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.
Interfaces cannot change without deprecation cycles, new interfaces can be added to address desired changes and the old interfaces marked for deprecation, which typically are removed after two major release cycles. Existing customers cannot have interfaces changes without time to accommodate them.
salt/states/junos.py
Outdated
@@ -158,15 +152,14 @@ def commit(name, **kwargs): | |||
|
|||
|
|||
@resultdecorator | |||
def rollback(name, id, **kwargs): | |||
def rollback(name, **kwargs): |
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.
see reply for salt/states/junos.py about deprecation cycle and changing interfaces
salt/states/junos.py
Outdated
return ret | ||
|
||
|
||
@resultdecorator | ||
def diff(name, d_id): | ||
def diff(name, **kwargs): |
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.
see reply for salt/states/junos.py about deprecation cycle and changing interfaces
The label of a positional argument doesn't really matter here compared to a documentation typo/error, but the positional argument is required otherwise the interface is changing without a deprecation cycle for the interface
@dmurphy18 Check if the changes are good now? |
Hi @sagetherage @cro @dmurphy18, Please help in getting this to closure. We want this to be part of Sodium release. Let us know if anything is to be done from our side. |
I have followed up internally as well @vnitinv with David Murphy and he will respond by no later than end of day, Monday 2020-04-27, he may respond sooner. |
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.
Apart from adding versionchanged for 'def diff' for the new extra kwargs, everything looks good, review wise.
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.
Thanks for the work
@vnitinv Some failing tests that need to be fixed before can merge |
@dmurphy18 I have fixed pre-commit failures. For ci/py3/macosxmojave looks like there is something that needs to be done from salt backend. Check the existing issue related to enum failure of Mac. #56603 |
What does this PR do?
Multiple bug fixes were done for Junos-related components in salt.
What issues does this PR fix or reference?
Tests written?
Yes