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 Allow multiseal to mismatch stored conf type into release/1.15.x #23694

Conversation

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

Backport

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

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


Fixes an error when going from single to multiple auto seals of the same
type


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/sgm/conf-mismatch-multiseal/namely-steady-rooster branch from 39b6c45 to 5e18715 Compare October 17, 2023 12:47
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/sgm/conf-mismatch-multiseal/namely-steady-rooster branch from ffc03c5 to 2fc2d59 Compare October 17, 2023 12:47
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Oct 17, 2023
@sgmiller sgmiller enabled auto-merge (squash) October 17, 2023 12:48
@sgmiller sgmiller added this to the 1.15.1 milestone Oct 17, 2023
@github-actions
Copy link

Build Results:
All builds succeeded! ✅

@sgmiller sgmiller merged commit 9c3e0fd into release/1.15.x Oct 17, 2023
@sgmiller sgmiller deleted the backport/sgm/conf-mismatch-multiseal/namely-steady-rooster branch October 17, 2023 13:03
@github-actions
Copy link

CI Results:
All Go tests succeeded! ✅

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.

2 participants