hyperlight-dev / hyperlight-dev/hyperlight-sandbox
Built-in credential resolver implementations (IMDS / Key Vault / OAuth)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 73
- Forks
- 7
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 23
Description
Follow-up from #89 (Scoped credentials for outgoing HTTP).
PR #89 ships only the resolver callback hook — no concrete resolver implementations (IMDS / Key Vault / OAuth) are included. These should land as separate, opt-in helpers (likely in their own crate) once the async resolver story (see related follow-up) is decided.
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
Start with the scoped-credentials resolver callback from #89 and read the related follow-up about the async resolver story. Clarify the intended boundaries for the IMDS, Key Vault, and OAuth implementations and their likely separate crate; done means the concrete helpers are defined as opt-in implementations after the async approach is decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100