cloud-foundation-fabric/organization-bootstrap/environments

Environment-based organizational sample

This sample creates an organizational layout with a single level, where each folder is usually mapped to one infrastructure environment (test, dev, etc.). It also sets up all prerequisites for automation (GCS state buckets, service accounts, etc.), and the correct roles on those to enforce separation of duties at the environment level.

This layout is well suited for medium-sized infrastructures managed by a small set of teams, where the complexity in application resource ownership and access roles is mostly dealt with at the project level, and/or in the individual services (GKE, Cloud SQL, etc.). Its simplicity also makes it a good starting point for more complex or specialized layouts.

Refer to the section-level README for general considerations about this type of samples, and usage instructions.

Managed resources and services

This sample creates several distinct groups of resources:

• one folder per environment
• one top-level project to hold Terraform-related resources
• one top-level project to set up and host centralized audit log exports (optional)
• one top-level shared services project

The number of resources in this sample is kept to a minimum so as to make it more generally applicable, further resources can be easily added by leveraging the full array of Cloud Foundation Toolkit modules, especially in the shared services project.

Shared services project

This sample contains a single, top-level project used to host services shared across environments (eg GCS, GCR, KMS, Cloud Build, etc.). In our experience, that is enough for many customers, especially those using this organizational layout.

For more complex setups where multiple shared services projects are needed to encapsulate a larger number of resources, shared services should be treated as an extra environment so that they can be managed by a dedicated set of Terraform files, using a separate service account and GCS bucket, with a folder to contain shared projects.

If no shared services are needed, the shared service project module can of course be removed from main.tf.

Inputs

Name	Description	Type	Default	Required
audit_viewers	Audit project viewers, in IAM format.	list	<list>	no
billing_account_id	Billing account id used as default for new projects.	string	n/a	yes
environments	Environment short names.	list(string)	n/a	yes
gcs_location	GCS bucket location.	string	"EU"	no
generate_service_account_keys	Generate and store service account keys in the state file.	string	"false"	no
grant_xpn_roles	Grant roles needed for Shared VPC creation to service accounts.	string	"true"	no
organization_id	Organization id.	string	n/a	yes
prefix	Prefix used for resources that need unique names.	string	n/a	yes
project_services	Service APIs enabled by default in new projects.	list	<list>	no
root_node	Root node for the new hierarchy, either 'organizations/org_id' or 'folders/folder_id'.	string	n/a	yes
shared_bindings_members	List of comma-delimited IAM-format members for the additional shared project bindings.	list	<list>	no
shared_bindings_roles	List of roles for additional shared project bindings.	list	<list>	no
terraform_owners	Terraform project owners, in IAM format.	list	<list>	no

Outputs

Name	Description
audit_logs_bq_dataset	Bigquery dataset for the audit logs export.
audit_logs_project	Project that holds the audit logs export resources.
bootstrap_tf_gcs_bucket	GCS bucket used for the bootstrap Terraform state.
environment_folders	Top-level environment folders.
environment_service_account_keys	Service account keys used to run each environment Terraform modules.
environment_service_accounts	Service accounts used to run each environment Terraform modules.
environment_tf_gcs_buckets	GCS buckets used for each environment Terraform state.
shared_resources_project	Project that holdes resources shared across environments.
terraform_project	Project that holds the base Terraform resources.