-
Notifications
You must be signed in to change notification settings - Fork 6
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
[feature-request] Allow setting up multiple npm tokens #6
Comments
I'd be open to work on this PR, but will need some guidance on how to go about it! |
Hey @arthurw1! I think the first step is to determine how the config will look like. Do you have any ideas here? e.g. - seek-oss/private-npm#v1.2.0:
registry:
- path: //registry.npmjs.org/
env: MY_ENV_VAR
- path: //myprivatenpm.com/
file: my_token_file |
Hi @72636c I was thinking of the following. Similar to your suggestion but without the
Do we need to accommodate for cases where |
LGTM! Let's start out with There's an example of parsing out a string list in the Docker ECR Cache plugin: https://github.com/seek-oss/docker-ecr-cache-buildkite-plugin/blob/d2a4b4763f2fe9c01a79eab10633bddcbc8e4f4c/hooks/lib/stdlib.bash#L23-L26. The code here may be slightly more involved since we'd be accessing nested names like |
I see. Will look into it! |
I ended up with a schema that is similar to your initial suggestion: - seek-oss/private-npm#v1.2.0:
multi-registries:
- path: //registry.npmjs.org/
env: MY_ENV_VAR
- path: //myprivatenpm.com/
file: my_token_file The feature is added and seems to be working when running |
We have a use case that requires us to pull deps from multiple private npm repositories, each requiring a unique npm token. Will it make sense to request for this feature in this plugin?
Thanks!
The text was updated successfully, but these errors were encountered: