-
Notifications
You must be signed in to change notification settings - Fork 912
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
Argument order for --decrypt #598
Comments
Yeah, this is not ideal and it’s an artifact of the CLI library we use. The
file name must go last, essentially, since it’s an argument and not a flag.
This is also not specific to —extract.
…On Fri, 20 Dec 2019 at 17:13, Donovan H. ***@***.***> wrote:
It took me a while to figure this out, but should argument order matter
here? 🤔
$ sops -d secrets.yaml
envSecrets:
deploy-key: 12345
$ sops -d secrets.yaml --extract '["envSecrets"]["deploy-key"]'
envSecrets:
deploy-key: 12345
$ sops -d --extract '["envSecrets"]["deploy-key"]' secrets.yaml
12345
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#598>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARH4V5CLEWV2BZAQ5X7MYLQZTVI3ANCNFSM4J573T2Q>
.
|
I think this should be detected and fail in case any parameters are passed after the file name. The reason why: I was also stuck on this for a bit until I realized my parameter order was incorrect. I found this issue since I accidentally used the same order as @heydonovan Should we open a new issue? Is that a bug or considered expected behavior? |
It's the same issue. It's considered a bug, and we definitely will welcome PRs that fix it, but it's a tricky one, since it'll affect lots of things and therefore will require some evidence that nothing was broken because of it. |
#1342 improves the situation by at least warning when this happens. |
It took me a while to figure this out, but should argument order matter here? 🤔
The text was updated successfully, but these errors were encountered: