8000 FTR: allow snapshot restore without initializing the cluster first · Issue #30611 · hashicorp/vault · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

FTR: allow snapshot restore without initializing the cluster first #30611

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

Open
azrdev opened this issue May 14, 2025 · 0 comments
Open

FTR: allow snapshot restore without initializing the cluster first #30611

azrdev opened this issue May 14, 2025 · 0 comments

Comments

@azrdev
Copy link
azrdev commented May 14, 2025

Is your feature request related to a problem? Please describe.

When restoring a raft snapshot as per the SOP https://docs.hashicorp.com/vault/tutorials/standard-procedures/sop-restore to a cluster, it has to be initialized and unsealed first. However, as stated in the SOP and in https://discuss.hashicorp.com/t/performing-restore-from-snapshot-invalidates-existing-auto-unseal-recovery-keys/55326 , all content of that cluster (especially unseal/recovery keys) is removed/overwritten with the backup content.

Thus the requirement to have an initialized+unseald cluster introduces a new set of secrets and operation procedure to deal with them (and mental capacity to separate them from the actually needed stuff), without actually needing these.

Describe the solution you'd like

Allow restoring into an empty cluster, which has not been initialized, and implicitly don't require unsealing in that case.

vault status tells me "Initialized: false", so the cluster knows if it has any content, and can distinguish that case from an initialized (possibly filled with content) but sealed cluster.

###Describe alternatives you've considered

Explain any additional use-cases

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
0