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

Correct the post-unseal meaning of the seal status type #23022

Merged
merged 5 commits into from
Oct 9, 2023

Conversation

sgmiller
Copy link
Collaborator

And at the same time add a RecoverySealType to the response which preserves the old meaning.
Updated the CLI to display both when relevant.

And at the same time add a RecoverySealType to the response which preserves the old meaning.
Updated the CLI to display both when relevant.
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Sep 12, 2023
@github-actions
Copy link

Build Results:
All builds succeeded! ✅

@github-actions
Copy link

CI Results:
All Go tests succeeded! ✅

@sgmiller sgmiller modified the milestones: 1.13.9, 1.15.1 Oct 5, 2023
@sgmiller sgmiller requested review from a team October 5, 2023 18:52
Copy link
Contributor

@ccapurso ccapurso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

Copy link
Contributor

@stevendpclark stevendpclark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

I'm assuming that the value multiseal with no additional details within this api end-point is acceptable for seal-ha instances to maintain backwards compatibility.

@sgmiller sgmiller merged commit 42a484c into main Oct 9, 2023
@sgmiller sgmiller deleted the sgm/vault-7061/correct-seal-status-types branch October 9, 2023 17:53
@ldilalla-HC ldilalla-HC removed this from the 1.15.1 milestone Oct 20, 2023
victorr pushed a commit that referenced this pull request Nov 16, 2023
* Correct the post-unseal meaning of the seal status type

And at the same time add a RecoverySealType to the response which preserves the old meaning.
Updated the CLI to display both when relevant.

* changelog

* no longer needed

* Don't need this field either, which fixes unit tests

* fix unit tests
victorr added a commit that referenced this pull request Nov 16, 2023
…nto release/1.15.x (#24170)

* Correct the post-unseal meaning of the seal status type (#23022)

* Correct the post-unseal meaning of the seal status type

And at the same time add a RecoverySealType to the response which preserves the old meaning.
Updated the CLI to display both when relevant.

* changelog

* no longer needed

* Don't need this field either, which fixes unit tests

* fix unit tests

---------

Co-authored-by: Scott Miller <[email protected]>
Co-authored-by: Victor Rodriguez <[email protected]>
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.

5 participants