> Our internal packaging teams biggest worry is that we don't want someone
to download something to their development laptop, compile the code into a
standalone binary, then deploy that out to our container platforms.
That's not really a problem with Go but an organizational problem.
You
How do you stop people from downloading and deploying arbitrary python or
java libs?
I can see that more than a developer policy is needed since it takes a
corrupt employee only one try to break the system before they’re caught,
and if the employee actually just made a mistake then firing them
Yes(technically) our deploys are controlled via gitlab.
Our internal packaging teams biggest worry is that we don't want someone to
download something to their development laptop, compile the code into a
standalone binary, then deploy that out to our container platforms.
In our production
Are the builds and deployment controlled? The command “go list” can be used
to simplify parsing the imports in each package, so a script could check
that every import is either an allowed standard library package or one
matching your internal URL.
Matt
On Wednesday, February 21, 2018 at
