While investigating FociSolutions/github-foundations-cli#2, we ran into an issue with the current repository setup:
There are effectively have 3 tools in the repo. One is the bootstrap terraform, another the organizations terragrunt, and the last, the gh_foundations Go cli.
We could simplify that to 2: The organization/bootstrap + Go cli, but we have only 1 release value per repo. If we want to release a new version of the terraform/terragrunt, and increment the release number, that means the go cli would also have to be recompiled and released, whether there are codes changes or not
ANALYSIS
There are a couple of obvious choices we could make:
Live with tying the same release to both (all three) tools, or
Separating the Go code into its own repo
For a few reasons, the 2nd option provides the most future flexibility, and will be the approach taken
ISSUE
While investigating FociSolutions/github-foundations-cli#2, we ran into an issue with the current repository setup:
There are effectively have 3 tools in the repo. One is the
bootstrapterraform, another theorganizationsterragrunt, and the last, thegh_foundationsGo cli.We could simplify that to 2: The
organization/bootstrap+Go cli, but we have only 1 release value per repo. If we want to release a new version of theterraform/terragrunt, and increment the release number, that means the go cli would also have to be recompiled and released, whether there are codes changes or notANALYSIS
There are a couple of obvious choices we could make:
For a few reasons, the 2nd option provides the most future flexibility, and will be the approach taken