Defined terms in the documentation for Terraform Example Foundation are capitalized and have specific meaning within the domain of knowledge.
The email for the privileged service accounts created in the seed project of the step 0-bootstrap. This service accounts are used to run Terraform by Cloud Build and Jenkins. When using Jenkins, the service account of the Jenkins Agent uses impersonation over this Terraform Service Accounts. A Terraform service account is created for each one of the steps.
Seed Project created in the 0-bootstrap step. It is the project where the Terraform Service Accounts (terraform_service_account) are created and hosts the GCS bucket used to store Terraform state of each environment in subsequent phases.
A project created in step 0-bootstrap to manage infrastructure within the organization.
The pipeline can use either Cloud Build, Github Actions, GitLab pipeline, Terraform Cloud or Jenkins depending on your context and Terraform is executed using the seed project service account.
Also known as the CI/CD project.
It is located under folder bootstrap.
A project created in step 4-projects to host a Cloud Build pipeline configured to manage application infrastructure within projects.
A separate pipeline exists for each of the business units and it can be configured to use a service account that has limited permissions to deploy into certain projects created in 4-projects.
They are located under folder common.
A Terraform Data Source that retrieves output values from a remote Backend Configuration.
In the Terraform Example Foundation context, it reads output values from previous steps like 0-bootstrap so that users don't need to provide again values given as inputs on previous steps or find the values/attributes of resources created in previous steps.