fix: support unenrypted vault files for templating#461
Merged
Conversation
joka134
marked this pull request as ready for review
June 5, 2026 09:02
Signed-off-by: joka134 <27293650+joka134@users.noreply.github.com>
NJona
approved these changes
Jun 5, 2026
NJona
left a comment
NJona
left a comment
Member
There was a problem hiding this comment.
lgtm as a hotfix until we decide on how we want to handle it.
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
2 participants
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.
This is hotfix to support recovery of bootstrapped GCP projects, where the vault has been encrypted before loading the vault for templating. We should discuss if we want to change the way of recovering the vault (decrypt on jumphost and download vs. download age_key.txt and decrypt when needed).