Dynamic ordering of resolvers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 34
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
There can be dependencies between resolvers. For instance, if resolver A needs to use an env var that is a secret resolved by B, nv needs to make sure all values resolved by B run first. Users should be able to configure which env vars a resolver uses, so nv can resolve them first if they are secret refs. In some cases, it may be possible to automatically identify env vars a resolver depends on too. nv will also need to account for the possibility of circular dependencies.
Contributor guide
No contributing guide indexed for this repository
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 mapping how resolvers are configured and executed, then define how resolver dependencies and secret environment references should be represented; done requires dependency-aware ordering and explicit handling of circular dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100