-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use authentication when running a package #4300
Use authentication when running a package #4300
Conversation
bca53d2
to
cbef0c4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A dyn Trait
should be a last resort, IMO.
It makes code more obtuse an harder to debug.
In this case, all it does it provide a token... why not just pass in the auth token as a setting?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now.
e279970
to
a63e75c
Compare
…Loader's public API to be more builder-like
…ageLoader over to resolve tokens from the URL hostname
a63e75c
to
2fec91a
Compare
As part of private packages and #4247, we want to make sure API tokens are sent to the backend when doing
wasmer run some/private-package
.We'd like the CLI to automatically figure out which token to use while not sending API tokens to random endpoints, so updated
WapmSource
(the component that queries the Wasmer registry when looking up packages) to accept an API token for its registry and modifiedBuiltinPackageLoader
(the component for downloading those packages) so it has a hashmap of hostnames to API tokens that it will consult when downloading a*.webc
file.