-
Notifications
You must be signed in to change notification settings - Fork 897
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
Decrypt with output-type dotenv panics on numbers #879
Comments
Duplicate of #857. |
It works now with sops 3.8.1, closing the issue. |
Oops, sorry, when I closed this as completed, I had accidentally tested this with a text string, and not a number. I still get an exception with a numerical value:
|
This is happening still. Any tracking on this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create a file
test.yaml
with just one key-value where the value consists of a number (i.e., integer or float). Plain decryption works fine:The same call but using
--output-type dotenv
panics:It's the same when using a float (
interface {} is float64, not string
), or when using a JSON instead of a YAML file. I stumbled upon this while trying asops exec-env
with a Docker .env-file that contains a port setting.The text was updated successfully, but these errors were encountered: