(un)encrypt options inconsistent for cli vs. config file
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Hi,
when trying to use the option --encrypted-regex '^data$' via command line everything works as expected.
when trying to use this option in the .sops.yaml it is ignored.
i figured out that in the config file i have to use encrypted_regex instead of encrypted-regex. so an underscore instead of the dash.
this is not pointed out under 4.9 Encrypting only parts of a file
if this is a well known this to everybody, but me, please excuse me filing this issue.
thanks
AndiY
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the documentation section “4.9 Encrypting only parts of a file” and the option forms --encrypted-regex and encrypted_regex described in the issue. Confirm how the CLI and .sops.yaml syntaxes differ, then update that section so the configuration-file spelling is explicit; the issue is done when users can find both forms there.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100