-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add provider class for Nautobot Secrets Functionality #49
Add provider class for Nautobot Secrets Functionality #49
Conversation
Co-authored-by: Glenn Matthews <glenn.matthews@networktocode.com>
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.
Looks good to me!
Co-authored-by: Glenn Matthews <glenn.matthews@networktocode.com>
Co-authored-by: Glenn Matthews <glenn.matthews@networktocode.com>
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.
LGTM
After discussions the config_context is the path forward on defining plugin(device) specific settings. |
@itdependsnetworks @dgarros anything else now that we have our path forward? This PR should be good to merge. |
Perhaps one question is whether to have two different options in the config on whether to use config_context for secrets then another one for extras (from other PR). I think one trigger should work. |
I think it should be 2 config keys. |
Was thinking {"use_config_context": {"secrets": True, "connection_options": True}} |
I like it |
Co-authored-by: Glenn Matthews <glenn.matthews@networktocode.com>
…bot-plugin-nornir into jkala-secrets-integration
fixes #44
This allows for secrets group feature to be used to provide username, password, secret.