Private Repository Support about go-mod-vendor HOT 6 CLOSED

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/165888910

The labels on this github issue will be updated when the story is started.

from go-mod-vendor.

Hi @cmccarthy101,
Thanks for filing this issue. We don't currently support this behavior in the go-mod-cnb and don't support this behavior in our go-buildpack as well. If you have dependencies in private repositories, an option could be to vendor your packages.

from go-mod-vendor.

There's some discussion on slack about this:
https://buildpacks.slack.com/archives/C94UJCNV6/p1557344013277100

In general, build-time environment variables can be used to inject credentials (e.g., --env-file with pack), but in this case, git can't read creds from environment variables.

I think we have a few options:

• A pack feature that lets you inject an SSH key
• A simple v3 buildpack that lets you inject an SSH key
• A simple v3 buildpack that creates a git credential helper from the environment (see the link above)

Regardless, not a feature that the go-mod-cnb should support directly.

from go-mod-vendor.

For now, we suggest that you vendor your modules as a workaround while we see abut prioritizing this feature. Let us know if this does is not possible for you. Thanks.

from go-mod-vendor.

Closing for now as a workaround was given. Definitely reopen if still an issue!

from go-mod-vendor.

Hi, kaniko are supporting injecting build vars (could be ssh key) that used in dockerfile. we using kaniko for now and try to make build more faster and easy for new service to onboard on our CI CD.

the question is, are pack will be able to do that? if its end up we build our own builder then whats different with creating our dockerfile cc @tillyt

from go-mod-vendor.