Terraform Control repo built following the pattern as outlined by Charity Majors
TLDR, but really, go read the post, it's way better then what I'm going to write here..
The Current production terraform version can be found here
- Clone the repo into a new directory for your project
git clone https://github.com/FitnessKeeper/terraform-reference terraform-<project name> - Edit .env in the root of the repo, in particular make sure you add a TF_PROJECT_NAME (this should be the new name of the repo,
terraform-<project name>)- When creating a
spikemake sure you update TF_SPINE in env if something other thenrkis needed, at the time of this writingrkandasicsare valid spines. - Also when creating ASICS
spikesupdate toTF_LOCK_TABLE=asics-services-terraformStateLock - If needed, set TF_STACK for the
stackvariable
- When creating a
- Initialize variables.tf, this only needs to be done once, when the repo is created run
./init-variables.tf.sh - Remove the old origin
git remote rm origin - Add your new repo
git remote add origin https://github.com/FitnessKeeper/terraform-<project name>.git - Commit your changes
git push -u origin master- Edit variables.tf to reflect your new service
cdinto the base dir for the env you want to work oncd terraform-<service>/env-development/
./init.sh# to initialize your environmentterraform get# to load your modulesterraform plan -var-file=development.tfvars# manage all the things!
We are trying to follow a pattern where we have an infrastructure repo with 3 tiers - dev, stage, and production, known as FitnessKeeper/terraform-runkeeper. We will use that control repo to build VPC, ECS Clusters, DNS Zones, and other resources that can be presented as a platform for use by services.
Services, will be created using atomic control repos, based off this skel, and have distinct state files for each of the tiers. In this way, we can make changes to the state of a service living atop our infrastructure, without having to push stage changes to the underlying resources.