[zachgersh]

RE: modules and vendoring, you should no longer have to worry about a package going away now that proxies have been introduced (the default proxy right now being proxy.golang.org).

You should be able to pull all your modules from a proxy, minus any private repos you control (which you can either setup our own proxy for OR set The GOPROXY var to go direct to vcs for it).

Also, not vendoring should give you a smaller repo and build speed shouldn’t suffer too much (proxy caching and such).

[sethammons]

modules and vendoring is still a pain and I don't want or need a network resource to build my code. If a vendor directory is present, use it!

While things are better in Go 1.14, it is not solved. I do not want to set up a company proxy for our private repos. I can't count how many times some combination of GOPROXY, private repos, vendoring, and modules have been a problem.

[swagonomixxx]

Ah good point about GOPROXY.

So if I have a mix of private and public dependencies that I pull in, can I specify a specific proxy for the private ones? Is it the GOPRIVATE env var?

[chairmanwow1]

The proxy should maintain a copy of all dependencies (public and private), so only one should be necessary.

[zachgersh]

This should be clarified, if you setup YOUR OWN proxy it can handle both public and private modules (side note I haven’t been able to verify this yet with artifactory).

You can also just let your GOPROXY fallback go “direct” which will then go straight to vcs (you need to make sure you have a gitconfig setup to redirect https to ssh).