Skip to content

Update development cluster known issue as fixed - #31223

Merged
blueberry-pi merged 2 commits into
mainfrom
vault-37317-update-known-issue
Jul 8, 2025
Merged

Update development cluster known issue as fixed#31223
blueberry-pi merged 2 commits into
mainfrom
vault-37317-update-known-issue

Conversation

@blueberry-pi

Copy link
Copy Markdown
Contributor

Description

Update the development cluster known issue created in 1.20.0 as fixed for 1.20.1. Also add a changelog entry. The known issue was created in #31067. The actual fix was merged in https://github.com/hashicorp/vault-enterprise/pull/8325.

Jira for the bug: https://hashicorp.atlassian.net/browse/VAULT-37317

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.

@blueberry-pi blueberry-pi added this to the 1.20.1 milestone Jul 8, 2025
@github-actions github-actions Bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 8, 2025
@github-actions

github-actions Bot commented Jul 8, 2025

Copy link
Copy Markdown

CI Results:
All Go tests succeeded! ✅

@blueberry-pi
blueberry-pi marked this pull request as ready for review July 8, 2025 15:37
@blueberry-pi
blueberry-pi requested review from a team as code owners July 8, 2025 15:37
@github-actions

github-actions Bot commented Jul 8, 2025

Copy link
Copy Markdown

Build Results:
All builds succeeded! ✅

@blueberry-pi
blueberry-pi merged commit 2f4b1c4 into main Jul 8, 2025
49 of 53 checks passed
@blueberry-pi
blueberry-pi deleted the vault-37317-update-known-issue branch July 8, 2025 16:30
Erfankam pushed a commit to Erfankam/vault that referenced this pull request Sep 1, 2025
* Update known issue as fixed

* add changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants