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

docs: fixed typo in kv v1 upgrade docs #29361

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Conversation

rathberm
Copy link
Contributor

Description

This PR fixes a typo/logical error in the KV v1 to KV v2 upgrade docs.
https://developer.hashicorp.com/vault/docs/secrets/kv/kv-v2/upgrade

The docs describe how the paths in KV v1 policies have to be migrated and prefixed with /data but the example does not show that, instead the engine is changed.

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

@rathberm rathberm requested a review from a team as a code owner January 16, 2025 09:02
Copy link

hashicorp-cla-app bot commented Jan 16, 2025

CLA assistant check
All committers have signed the CLA.

@jonathanfrappier
Copy link
Contributor

@rathberm - thanks for catching that and submitting a PR!

@jonathanfrappier jonathanfrappier merged commit 4536c98 into hashicorp:main Jan 16, 2025
46 of 50 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants