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.
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.