Keep metadata around in decrypted version so that file can be re-encrypted with same settings
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
I would suggest an option to keep metadata around in decrypted version of the YAML file so that file can be re-encrypted with same settings, without having to have .sops.yml file around. So I could send encrypted file to a friend, they could decrypt it, change things, and encrypt it back. With all metadata for both operations in the file.
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
No files, tests, or entry points are named in the issue. The requested outcome is an option that preserves all encryption metadata in the decrypted YAML so it can be changed and re-encrypted with the same settings without a .sops.yml file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, yaml
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100