Skip to content

Add Vault 1.20 known issue for UI Error in Vault 1.20 with secrets with underscores VAULT-37528 - #31202

Closed
owenzorrin wants to merge 1 commit into
hashicorp:mainfrom
owenzorrin:patch-1
Closed

Add Vault 1.20 known issue for UI Error in Vault 1.20 with secrets with underscores VAULT-37528#31202
owenzorrin wants to merge 1 commit into
hashicorp:mainfrom
owenzorrin:patch-1

Conversation

@owenzorrin

@owenzorrin owenzorrin commented Jul 3, 2025

Copy link
Copy Markdown
Contributor

Add Vault 1.20 known issue from https://hashicorp.atlassian.net/browse/VAULT-37528

Description

What does this PR do?

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.

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.
  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
  • If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

@owenzorrin
owenzorrin requested review from a team as code owners July 3, 2025 17:10
@hellobontempo

Copy link
Copy Markdown
Contributor

FYI this is a duplicate of: #31202

@owenzorrin

Copy link
Copy Markdown
Contributor Author

Closing duplicate PR, please review and approve #31147

@owenzorrin owenzorrin closed this Jul 3, 2025
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