Simplify adding a new internal customer feature request (Terraform root module) to the platform

[brettcurtis]

When adding a new Terraform root module to the platform, several pull requests must happen across multiple repos. In this example, we must enable Google Artifact Registry to allow teams to store containers and use virtual repos for Docker Hub. This will also allow teams to use GKE image streaming. You often add new features your internal customers request throughout your platform journey. This is just one example of that.

Pull Requests:

• Create a repository: Add or update repository github-organization-management#142
  • Once this is done, usually copying/pasting code from another root module is the best approach to bootstrapping
• Create the Terraform backend: Add or update Terraform backend google-cloud-terraform-backend#177
• Setup the Google Cloud Platform Hierarchy:
  • Add folder: Add or update folder and identity groups google-cloud-hierarchy#194
  • Add folder IAM roles: Add folder IAM roles google-cloud-hierarchy#195

At this point, any IaC in the new Terraform root module will be able to flow through the continuous delivery flow. Given all that is happening on the backend, this isn't terrible, but let's see what we can do to improve this flow.

Tasks

Preview Give feedback

1. Folder IAM policies have a dependency on unknown folder IDs google-cloud-hierarchy#167
   +0