fix(local): always load the local prod.vault.yaml file unencrypted - #619
Open
schrodit wants to merge 1 commit into
Open
fix(local): always load the local prod.vault.yaml file unencrypted#619schrodit wants to merge 1 commit into
schrodit wants to merge 1 commit into
Conversation
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.
The local installer writes the file unencrypted and then encrypts them to the secrets dir where is then used by the real installer.
The local development flow is intended to be as easy as possible and should not contain production environments this file is kept unecrypted.
Currently we force it to be encrypted which fails most local flows.