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

Backport of ignore leading slash in kv get command into release/1.11.x #16490

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #16443 to be assessed for backporting due to the inclusion of the label backport/1.11.x.

The below text is copied from the body of the original PR.


Handling of leading slashes was not consistent in the vault kv get command. This can be fixed by simply ignoring the leading slash of the requested path. The following will all successfully fetch a secret at path secret/foo:

vault kv get /secret/foo

vault kv get secret/foo

vault kv get -mount=secret /foo

vault kv get -mount=secret foo

Fixes #16238


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/fix-kv-get-leading-slash/presumably-promoted-oyster branch from 68fb96f to 2889acc Compare July 28, 2022 18:13
@ccapurso ccapurso enabled auto-merge (squash) July 28, 2022 18:17
@ccapurso ccapurso merged commit 0935c8b into release/1.11.x Jul 28, 2022
@ccapurso ccapurso deleted the backport/fix-kv-get-leading-slash/presumably-promoted-oyster branch July 28, 2022 19:16
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.

2 participants