elegant-portugal-58808
01/08/2025, 5:16 PM~/.npmrc
properly set to read from GitHub's npm registry.
@<gh-org>:registry=<https://npm.pkg.github.com>
//npm.pkg.github.com/:_authToken=<gh-token>
Has anyone worked around this authentication for private Pulumi package registries? I would appreciate it if anyone could help.
I already tried to disable the default package installation + pass my token via env vars + write .npmrc via Pre-run commands
but the .npmrc generated in that context seems not to affect yarn/npm, i.e., they keep trying to pull from the default npm registry, ignoring the registry instruction of my .npmrc.
I also tried to use a custom container image where I would rewrite the .npmrc using envsubst
to put my token there! But I also had issues with this approach as the custom executor image doesn't let me pass -e
parameters to make the container's environment filled with the needed token and therefore I got a 401 due to the missing token.elegant-portugal-58808
01/09/2025, 11:41 AMincalculable-plumber-44531
01/20/2025, 9:43 AMpulumi preview
or pulumi up
when it's containerised?No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.
Powered by