Skip to content

Conversation

billy4479
Copy link

@billy4479 billy4479 commented Sep 2, 2025

Closes #1914 (supersedes).
Fixes #879.
Fixes #1167 (as no longer applies).

Rebased on top of #1929.

When decrypting to dotenv we try to escape new line in the values
without taking into account the possibility that the value could be
something different than a string (e.g. an int).

This used to cause a panic when using `decrypt --output-format dotenv`.

Signed-off-by: billy4479 <giachi.ellero@gmail.com>
This was previously forbidden for some reason, however if the value is
not a complex type there should be no issues.

Signed-off-by: billy4479 <giachi.ellero@gmail.com>
@felixfontein
Copy link
Contributor

Rebasing my PR and then merging main into your branch wasn't the best idea I ever had... 🤦 I've rebased so that now only your commits are left. If you prefer, please rebase so that the commits are properly yours.

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

Successfully merging this pull request may close these issues.

Document that exec-env does not work when encrypted values are of types other than strings Decrypt with output-type dotenv panics on numbers
2 participants