Skip to content
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] Provide credentials to npm trough environment variables #290

Closed
Kuinox opened this issue Nov 7, 2019 · 2 comments
Closed

[FEATURE] Provide credentials to npm trough environment variables #290

Kuinox opened this issue Nov 7, 2019 · 2 comments
Labels
Enhancement new feature or improvement

Comments

@Kuinox
Copy link

Kuinox commented Nov 7, 2019

What / Why

Today the only way to give npm the PAT to push packages is to add the PAT in the .npmrc.
In order to authenticate, our CI must inject the credentials in the .npmrc, then revert the change when the operation is done.
It would be far better if we could give credentials to npm directly via environment variables, so we can stop using this "workaround".

@Kuinox Kuinox changed the title [FEATURE] Provide credentials to npm trough environement variables [FEATURE] Provide credentials to npm trough environment variables Nov 7, 2019
@darcyclarke darcyclarke added Bug thing that needs fixing Enhancement new feature or improvement and removed Bug thing that needs fixing labels Nov 8, 2019
@darcyclarke darcyclarke modified the milestone: OSS - Sprint 17 Oct 5, 2020
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

1 similar comment
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement new feature or improvement
Projects
None yet
Development

No branches or pull requests

2 participants