Migrate Terraform & Bootstrapping from Cas-Reg to Cas-Pipeline for use in Cas-Reporting

[joshgamache]

We have a Terraform bootstrap setup in Cas-Registration that should be used to do the same in Cas-Reporting. This can be moved to Cas-Pipeline, which can then be used to bootstrap resources for Reporting.

• [x] Move Terraform & bootstrapping scripts (mostly in the /devops folder and root's Makefile) Cas-Pipeline

  • [x] Images and core config can live in this repo (superceeding the existing Terraform Cloud config)
  • [x] Repo specific scripts should live with their repos (ie. Terraform scripts to make storage for backups)
  • [x] Terraform credentials can live centrally with Cas-Pipeline (set up once)

• [x] Terraform scripts to provision GCS resources for Cas-Reporting

  • [x] Any credentials for resources created by Terraform should live in target repos/clusters

Once established, these can be used for parallel Terraform Cloud offboarding tasks such as CIF 1333.

Notes

See Moose ZH #11 & Moose PR #246 for parrallel cas-Registration work.

[mikevespi]

The Postgres instance that is in use in Registration is the one we'll be using for Reporting, so no need to make a new one now. It has been split off into its own repo. The init Terraform code should indeed be moved over, so creating the bucket for it, creating the service account in OC to be used for TF commands etc. Anything that will be run on all of the repos can be moved to Cas-Pipeline. Anything Terraform that is codebase specific will live in that repo. So Registration specific TF code can go in Reg, so on. I think that this ticket can be scoped to moving that init code over to Cas-Pipeline. Reporting itself has nothing to deploy yet, but this portion will affect Reg and free us up to move the legacy apps off of TFCloud.