Skip to content
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

Merged
merged 16 commits into from
Apr 19, 2023
Merged

Add Hashicorp Kv v1 support #53

merged 16 commits into from
Apr 19, 2023

Conversation

k0rventen
Copy link
Contributor

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 new kv_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.

@jathanism
Copy link
Contributor

Hi @k0rventen this seems like a great change. Would love to see you wrap it up so we can get it added!

@k0rventen
Copy link
Contributor Author

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 ?

@k0rventen k0rventen marked this pull request as ready for review February 3, 2023 01:00
@bryanculver bryanculver requested a review from a team as a code owner April 19, 2023 16:07
@bryanculver
Copy link
Member

@nautobot/core please give a review then I'll batch this in with the next release hopefully today

…s/home.html

Co-authored-by: Glenn Matthews <glenn.matthews@networktocode.com>
@bryanculver bryanculver merged commit 5355cf0 into nautobot:develop Apr 19, 2023
@bryanculver bryanculver mentioned this pull request Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants