-
Notifications
You must be signed in to change notification settings - Fork 886
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
Allow to pass multiple paths to 'updatekeys' #1274
Conversation
2184382
to
319c322
Compare
c6fb84d
to
0cde35a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
404355f
to
7488de6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current version makes the return value less usable. I'm not sure whether anyone relied on the return values of the updatekeys
command, but in case any did, they are now broken.
How about slightly adjusting the behavior so that in case there is one argument, the old code is used, and if there are at least two arguments, the new code is used?
de99cef
to
978514f
Compare
Adjusted. I'm also now printing the amount of failed key updates when multiple arguments are used. I hope that's fine. |
978514f
to
071193c
Compare
Signed-off-by: Simon Jürgensmeyer <[email protected]>
071193c
to
b693f29
Compare
@sj14 thanks for your contribution! |
Allow to pass multiple paths to the
updatekeys
command, e.g.sops updatekeys file1 file2 file3
.