Add warning / force option when overwriting files #1976
DennisGaida
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As the documentation says to use
sops encrypt file > file.enc
it is the first thing I tried, but didn't like that it just overwrites files without asking before doing so. I thought the--output
option would alleviate that and warn me when writing to an existing file - nope. This is actually how I got to checking out the CLI documentation with a small word error: #1975Anyways, I would love if the
--output
option would not just overwrite a file without asking. This may be any file anywhere so I believe it is quite a dangerous operation. I would love if we had a-y/--yes
option or a--force
option that would need to be added to not have any warnings. This goes forsops encrypt --output <file>
as well as forsops decrypt --output <file>
.I know this would be a breaking change, but it frightens me a bit using
sops
(just likerm -rf
is always frightening, but it already has thef
for fearnot) without any check for existing files.Beta Was this translation helpful? Give feedback.
All reactions