-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Update some cliconf plugins #47141
Update some cliconf plugins #47141
Conversation
Hi @Qalthos, thank you for submitting this pull-request! |
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.
iirc we discussed using kwargs and opted to not use it in favor of well-defined API signature.
I think it is safe add this change for all the remaining community platforms that has cliconf
plugins
Looks like nos.py needs the same change? |
@LindsayHill good catch, added |
@Qalthos thanks for adding that - saved me doing it. The NOS modules are pretty new, and I want them to stay in line with the Ansible Network Team-developed modules as much as possible |
* Add `check_all` to many community cliconf plugins (cherry picked from commit 7844a40) Co-authored-by: Nathaniel Case <this.is@nathanielca.se>
Just curious, does anyone happen to know what version of Ansible this will be included with? A patch release for 2.7 (2.7.1, 2.7.2, etc..) or 2.8? |
@mfisher30 follow the PR referenced above See
|
* Add `check_all` to many community cliconf plugins
SUMMARY
Exposes network_cli functionality to more platform cliconf plugins.
Query: Most of these options pass straight through to network_cli. Would a
**kwargs
for those options be acceptable, in order to reduce work on cliconf plugins?Fixes #47143
ISSUE TYPE
COMPONENT NAME
cliconf/aireos
cliconf/edgeos
many more
ANSIBLE VERSION