<p>Lets say for example, you have a github repo that handles your infrastructure for an application. We'll call this repo <code>infrastructure</code>. It has some Terraform scripts, some Ansible scripts, etc. Now lets say you want to glue it all together with a Go binary that you build.</p>
<p>If this were Ruby or Python, I would write a simple script with various commands to interface with the above tools, and I would include it with the above repo.</p>
<p>For Go, what is the intended way to accomplish this? Do I:</p>
<ol>
<li><p>create a separate repo in my Go workspace called <code>infrastructure_builder</code> (for example), then create a binary, and store that in the <code>infrastructure</code> repo with my above project?</p></li>
<li><p>have the Go source files co-exist in the same repo as my <code>infrastructure</code> project, and build a binary perhaps on deployment of that project. If I did this, how does that work as far as the Go workspaces?</p></li>
<li><p>or because I plan to glue this together with Go, simply put all the above <code>infrastructure</code> project, in the Go workspace and have the Go source code live alongside it.</p></li>
</ol>
<p>Or is there another way of handling this?</p>
<hr/>**评论：**<br/><br/>Zikes: <pre><p>I like to use <code>make</code>, since it's fairly standard. One of the great things about this is make can assume that Go is installed on the builder machine, so you can <code>go get</code> other Go tools and run project "scripts" with <code>go run some_script.go</code>.</p></pre>mcandre: <pre><p>To begin with, version control the scripts into some git repositories. Bundle into a Docker container, RPM, DEB, TGZ, or such. Gradually replace each script with a pure Go equivalent.</p></pre>antiphase_: <pre><p>Why, in the name of all that is good and holy, would you put a script into a Docker container?</p></pre>mcandre: <pre><p>Not for transport, for installation. Glue code is a vague term. If the script is meant to function as part of a machine, then install it so. If, on the other hand the script is meant to manage machines, and be invoked by humans, then just keep it in a git repository.</p></pre>sacrehubert: <pre><p>To avoid the usual "it works on <em>my</em> machine..." issues.</p></pre>dtirer: <pre><p>To clarify what I mean by glue scripts. Before running any terraform commands, we have to make sure that:</p>
<ul>
<li><p>terraform init has been run in the correct environment . </p></li>
<li><p>that any terraform modules have been downloaded . </p></li>
<li><p>we need to grab a couple secrets from AWS Parameter Store that serve as input to Terraform . </p></li>
<li><p>etc... </p></li>
</ul>
<p>So I'm looking write a script that encapsulates some of these things in single commands like: <code>builder init staging</code>, and so forth</p></pre>
