[minor] Restore automatic KMS recovery custody - #30
Merged
Conversation
libops-agent
force-pushed
the
kms-gcs-recovery
branch
from
August 28, 2026 13:24
0265d50 to
052ffb1
Compare
libops-agent
force-pushed
the
kms-gcs-recovery
branch
from
August 28, 2026 13:26
052ffb1 to
f82651e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Restore the established automatic recovery flow: Vault returns recovery shares to the initializer, which removes the initial root token, encrypts the recovery bundle with Google KMS, and writes only ciphertext to create-only GCS storage. Optional custodian PGP keys remain supported. X-Admin-Token remains unchanged.