Feature Request: --recursive for inplace encryption/decryption, given 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
Motivation
I would like to use sops for kubernetes in the sense of storing encrypted files in git and then as the normal deploy flow
- decrypt everything
- build kubernetes yaml files and apply them
- encrypt everything
I think this workflow is also useful for many others.
Current Status
So far one has to write a manual for loop with sops -d -i mycurrentfile and sops -e -i mycurrentfile, and ignore if sops throws an error like error loading config: no matching creation rules found.
Feature Request
It would be great if the standard sops command has a --recursive flag which can be combined with -d -i and -e -i to recursively apply the rules in .sops.yaml to all the files in the current directory and subdirectories. If something is not in the .sops.yaml rules, it should not be touched.
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
Start at the standard sops command handling for -d -i and -e -i, then trace how .sops.yaml creation rules are applied. Implement recursive processing for the current directory and subdirectories while leaving files without matching rules untouched; no specific source files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100