Add ability to strip encrypted or unencrypted suffix on decryption
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
This would allow the use of sops without needing to update key names in the areas that they are used to have _encrypted or _unencrypted.
Encrypted example:
db:
password_encrypted: ENC[...]
Upon decryption with a "strip suffix option":
db:
password: pw123
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
The issue provides encrypted and decrypted YAML examples but names no files, tests, or entry points. Start by locating the decryption option handling and reviewing the existing issue discussion; done means an optional suffix-stripping behavior for encrypted and unencrypted keys, with existing decryption behavior unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100