-
Notifications
You must be signed in to change notification settings - Fork 158
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 should emit json for the entire item #50
Comments
Or even without the proposed "-F json" |
I like both. :-) -F for changing the format seems reasonable and follows the same feel of the data bag commands where you can pass in -F (summary, text, json, yaml, or pp). This feels natural and will update it, unless you have a branch with it in it that you want to PR to me. Making VALUES optional also seems natural to me and follows the knife data bag show [bag] [item] paradigm. If you supply VALUES you can filter the things returned, if you don't then you get the whole vault item returned. Again, will make that change unless you have a branch with it in it to PR to me. Thanks guys, good suggestions! |
I can update an existing vault item from json that contains multiple values, e.g.: zs-api.json:
then
It seems I also should be able to emit json for bulk edits and re-uploading, e.g: the following should work:
so I can bulk edit and update the vault more consistently.
The text was updated successfully, but these errors were encountered: