I've been having some great results converting some of my internal projects from glide to go modules, but I am looking at a specific workflow right now that is confusing me. Hoping to get some clarification...
Project 'foo' has its dependencies vendored via "go mod vendor". This works great when building that project internally since a non-go developer can clone the project and build it, with no external proxy access needed to download dependencies.
Now I am trying to allow project 'bar' to build a tool provided by 'foo'. The go.mod file only contains:
What I am seeing is that foo and all of its dependencies will be clones from their origins, and my go.sum file is updated with all of the transient dependencies. But what I really want is to only fetch 'foo' from my internal network and to have it use the vendored dependencies.
Is this even possible? The "-mod=vendor" flag was very useful when building project "foo" directly. But it doesn't seem to apply here because project "bar" doesn't want to vendor. It wants to get the one primary dependency and that is it.
Justin