-
Notifications
You must be signed in to change notification settings - Fork 14
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 Hashicorp Kv v1 support #53
Conversation
Hi @k0rventen this seems like a great change. Would love to see you wrap it up so we can get it added! |
Thx @jathanism , I've added the missing doc in various places and added the tests for the kv1 to the test harness, but I'm unable to launch the tests locally using poetry/invoke (same issue as in #49). Could one of the maintainer approve the review to enable the tests on the CI side ? |
Co-authored-by: nniehoff <github@nickniehoff.net>
@nautobot/core please give a review then I'll batch this in with the next release hopefully today |
nautobot_secrets_providers/templates/nautobot_secrets_providers/home.html
Outdated
Show resolved
Hide resolved
…s/home.html Co-authored-by: Glenn Matthews <glenn.matthews@networktocode.com>
this PR adds support for the kv engine v1 on the Hashicorp provider.
The changes are minimal, as the only thing that changes is the path of the secret, where in v2 a
/data
is added compared to v1.By default the version is
v2
to retain backwards compatibility. A newkv_version
argument is available in the secrets.I haven't changed the tests yet, but I've tested the functionality locally against a vault with v1 kv engine. This first iter is just to make sure that the initial tests & CI is still working OK with my changes before making changes.