Support for custom YAML tags
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Is it possible to support custom YAML tags?
key_unencrypted: !env SOMEVAR
Currently, these tags get removed by sops and only the plain value ("SOMEVAR") remains.
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 names no files, tests, or entry points. Start by locating the YAML parsing and serialization paths in the repository, then trace how tags such as !env are handled. Done means custom tags survive SOPS processing without losing the associated value, with coverage for the shown YAML example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, yaml
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100