Fetch npm package from private github or google repo. about cloud-builders HOT 7 CLOSED

Hey!

We don’t have an integrated solution as of today, but here are a few solutions coming from users:

1. Create a Github token with “repo” scope, then use this syntax in the package.json:

"my-private-module": "git+https://<github_token>:[email protected]/<user>/<repo>.git"

2. Use a Deploy or User Key that you could store in GCS for example, and pull it as a previous build step.

I hope this helps.

from cloud-builders.

This newly-published doc on Using Encrypted Files in your build should be helpful.

from cloud-builders.

I have a "hack" not what I would call a "solution" to this problem. It involves,

1. Make a copy of package.json
2. Download private repo, using either gcloud builder or git buider.
3. remove private repo from package.json
4. run npm install.
5. copy private repo to node_modules.
6. replace package.json with original.
7. run npm rebuild.
8. build image.

It's not elegant.

from cloud-builders.

Thanks, @Philmod, the only problem with that approach, is that if you don't commit the url including the github token to GitHub, you will have to do some kind of "sed" like replacement in package.json. You would have to do it both on the developer side and the builder side, or .gitignore package.json and copy package.json.builder to package.json, all of which is messy. I think i'll need to do the same thing that i did with kubectl bring the git auth in from GCS and configure git. Like it is on my dev box.

from cloud-builders.

Wow, thanks @bendory, that is simple and effective. Way better than storing the account.json file in gs//.

from cloud-builders.

Great! So glad you like it!
Shall we close this issue?

from cloud-builders.

I'm closing this issue with the assumption that our doc on Using Encrypted Files resolves this issue. Please re-open if that does not provide you with what you need.

from cloud-builders.