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

Allow use of private configs #9

Open
eviln1 opened this issue Mar 17, 2023 · 0 comments
Open

Allow use of private configs #9

eviln1 opened this issue Mar 17, 2023 · 0 comments

Comments

@eviln1
Copy link

eviln1 commented Mar 17, 2023

I would like to be able to use commitlint configs from private packages or repositories.

I believe this is not currently possible for the following reasons:

  • Passing NPM_TOKEN environment variable through contexts or project configuration is not sufficient, because without the -E switch, sudo drops environment variables.
  • Even if -E switch was used, any .npmrc config present in the project would not be read.
  • The orb doesn't allow overriding the executor or the docker image, so I cannot use an image which running as root such as node:18.14
  • AFAICT npm doesn't allow passing _authToken on the CLI, meaning I cannot piggy-back the configs parameter to inject CLI options.
  • I can't attach a workspace with node_modules where I would have previously installed the private package.
  • I can't write a custom job re-using a command from the orb, because there are none.

I will gladly open a PR to address this, but I'd like to know what would be your favorite method of solving this.

Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant