You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
% sops -d secrets.enc.env --output-type json
<command prints secrets in the env file, but in a JSON object container instead>
Actual
% sops -d secrets.enc.env --output-type json
<command behaves as though `--output-type` was not given
Workaround
Moving --output-type json in front of -d <path>does work:
% sops --output-type json -d secrets.enc.env
<expected output as described above>
Not sure if this is expected behavior and thus a docs gap, or a bug. I'd guess the latter since sops --help says that everything is just a "global option" with no relative order required for them to work.
The text was updated successfully, but these errors were encountered:
Also please note that -d path are two separate options: a flag (-d) and a positional argument (path). All options must come before the positional arguments. So sops -d --output-type json secrets.enc.env will work as well.
On sops 3.7.3:
Expected
Given an encrypted .env file,
Actual
Workaround
Moving
--output-type json
in front of-d <path>
does work:Not sure if this is expected behavior and thus a docs gap, or a bug. I'd guess the latter since
sops --help
says that everything is just a "global option" with no relative order required for them to work.The text was updated successfully, but these errors were encountered: