hyperlight-dev / hyperlight-dev/hyperlight-sandbox
Async resolver path for scoped HTTP credentials
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).
The credential resolver callback is currently a synchronous Fn() -> Result<String, String> that runs on the WASI HTTP dispatch thread. Production resolvers (IMDS, OAuth refresh, Key Vault) need async support plus caching/refresh. For now, caching is delegated to the resolver implementer.
A future change should introduce an async resolver variant without breaking the existing sync surface.
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 by reviewing issue #89 and the existing synchronous credential resolver surface described here, including its execution on the WASI HTTP dispatch thread. Define how an asynchronous resolver variant can support production resolvers while preserving the current synchronous API; done means the compatibility boundary and async behavior are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100