Make encrypt input and decrypt STOUT symmetrical #32
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
The problem here is that the previous output appended log information to STDOUT ```bash Secure-env : INFO SENTRY_DSN=something BING_SUBSCRIPTION_KEY=something_else ``` This has now become an invalid `.env` file. This made it difficult to use this in combination with other tools, e.g. to regenerate a local `.env` file as part of a build tool. My recommendation here is to remove this meta-information when decrypting such that we get ```bash SENTRY_DSN=something BING_SUBSCRIPTION_KEY=something_else ```
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 problem here is that the previous output appended log information to STDOUT
Secure-env : INFO SENTRY_DSN=something BING_SUBSCRIPTION_KEY=something_elseThis has now become an invalid
.envfile.This made it difficult to use this in combination with other tools, e.g. to regenerate a local
.envfile as part of a build tool.My recommendation here is to remove this meta-information when decrypting such that we get