Expose full config via Go API
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Hi,
I am working on a project where I would like to use SOPS as the secret engine. In this context, I want to be agnostic whether the user is using my CLI or sops to interact with the secret, but that requires that I generate the .sops.yaml in their repository.
Currently, there is no simple public Load function that returns a Config and I am wondering if that is by design. My use-case requires both the full config creation_rules and destination_rules.
I am happy to implement this, but I wanted to know if I am not doing anything wrong here.
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 by tracing the existing configuration-loading path and the Config type mentioned in the issue, then determine how creation_rules and destination_rules are currently represented. Done means agreeing on and exposing a public Go API that returns the full configuration, with coverage for both rule sets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100