Google Cloud Project Factory Terraform Module

This module allows you to create opinionated Google Cloud Platform projects. It creates projects and configures aspects like Shared VPC connectivity, IAM access, Service Accounts, and API enablement to follow best practices.

To include G Suite integration for creating groups and adding Service Accounts into groups, use the gsuite_enabled module.

Compatibility

This module is meant for use with Terraform 0.13. If you haven't upgraded and need a Terraform 0.12.x-compatible version of this module, the last released version intended for Terraform 0.12.x is 9.2.0.

Upgrading

See the docs for detailed instructions on upgrading between major releases of the module.

Usage

There are multiple examples included in the examples folder but simple usage is as follows:

module "project-factory" {
  source  = "terraform-google-modules/project-factory/google"
  version = "~> 10.1"

  name                 = "pf-test-1"
  random_project_id    = true
  org_id               = "1234567890"
  usage_bucket_name    = "pf-test-1-usage-report-bucket"
  usage_bucket_prefix  = "pf/test/1/integration"
  billing_account      = "ABCDEF-ABCDEF-ABCDEF"
  svpc_host_project_id = "shared_vpc_host_name"

  shared_vpc_subnets = [
    "projects/base-project-196723/regions/us-east1/subnetworks/default",
    "projects/base-project-196723/regions/us-central1/subnetworks/default",
    "projects/base-project-196723/regions/us-central1/subnetworks/subnet-1",
  ]
}

Features

The Project Factory module will take the following actions:

Create a new GCP project using the project_name.
If a shared VPC is specified, attach the new project to the svpc_host_project_id.

It will also give the following users network access on the specified subnets:
- The project's new default service account (see step 4)
- The Google API service account for the project
- The project controlling group specified in group_name
Delete the default compute service account.
Create a new default service account for the project.
1. Give it access to the shared VPC (to be able to launch instances).
Attach the billing account (billing_account) to the project.
Give the controlling group access to the project, with the group_role.
Enable the required and specified APIs (activate_apis).
Delete the default network.
Enable usage report for GCE into central project bucket (target_usage_bucket), if provided.
If specified, create the GCS bucket bucket_name and give the following accounts Storage Admin on it:
1. The controlling group (group_name).
2. The new default compute service account created for the project.
3. The Google APIs service account for the project.

The roles granted are specifically:

New Default Service Account
- compute.networkUser on host project or specified subnets
- storage.admin on bucket_name GCS bucket
group_name is the controlling group
- compute.networkUser on host project or specific subnets
- Specified group_role on project
- iam.serviceAccountUser on the default Service Account
- storage.admin on bucket_name GCS bucket
Google APIs Service Account
- compute.networkUser on host project or specified subnets
- storage.admin on bucket_name GCS bucket

Shared VPC subnets and IAM permissions

A service project's access to shared VPC networks is controlled via the roles/compute.networkUser role and the location to where that role is assigned. If that role is assigned to the shared VPC host project, then the service project will have access to all shared VPC subnetworks. If that role is assigned to individual subnetworks, then the service project will have access to only the subnetworks on which that role was assigned. The logic for determining that location is as follows:

If var.svpc_host_project_id and var.shared_vpc_subnets are not set then the compute.networkUser role is not assigned
If var.svpc_host_project_id is set but no subnetworks are provided via var.shared_vpc_subnets then the compute.networkUser role is assigned at the host project and the service project will have access to all shared VPC subnetworks
If var.svpc_host_project_id is set and var.shared_vpc_subnets contains an array of subnetworks then the compute.networkUser role is assigned to each subnetwork in the array

Inputs

Name	Description	Type	Default	Required
activate_api_identities	The list of service identities (Google Managed service account for the API) to force-create for the project (e.g. in order to grant additional roles). APIs in this list will automatically be appended to `activate_apis`. Not including the API in this list will follow the default behaviour for identity creation (which is usually when the first resource using the API is created). Any roles (e.g. service agent role) must be explicitly listed. See https://cloud.google.com/iam/docs/understanding-roles#service-agent-roles-roles for a list of related roles.	list(object({ api = string roles = list(string) }))	`[]`	no
activate_apis	The list of apis to activate within the project	`list(string)`	[ "compute.googleapis.com" ]	no
auto_create_network	Create the default network	`bool`	`false`	no
billing_account	The ID of the billing account to associate this project with	`string`	n/a	yes
bucket_force_destroy	Force the deletion of all objects within the GCS bucket when deleting the bucket (optional)	`bool`	`false`	no
bucket_labels	A map of key/value label pairs to assign to the bucket (optional)	`map`	`{}`	no
bucket_location	The location for a GCS bucket to create (optional)	`string`	`"US"`	no
bucket_name	A name for a GCS bucket to create (in the bucket_project project), useful for Terraform state (optional)	`string`	`""`	no
bucket_project	A project to create a GCS bucket (bucket_name) in, useful for Terraform state (optional)	`string`	`""`	no
bucket_versioning	Enable versioning for a GCS bucket to create (optional)	`bool`	`false`	no
budget_alert_pubsub_topic	The name of the Cloud Pub/Sub topic where budget related messages will be published, in the form of `projects/{project_id}/topics/{topic_id}`	`string`	`null`	no
budget_alert_spent_percents	A list of percentages of the budget to alert on when threshold is exceeded	`list(number)`	[ 0.5, 0.7, 1 ]	no
budget_amount	The amount to use for a budget alert	`number`	`null`	no
budget_monitoring_notification_channels	A list of monitoring notification channels in the form `[projects/{project_id}/notificationChannels/{channel_id}]`. A maximum of 5 channels are allowed.	`list(string)`	`[]`	no
consumer_quotas	The quotas configuration you want to override for the project.	list(object({ service = string, metric = string, limit = string, value = string, }))	`[]`	no
create_project_sa	Whether the default service account for the project shall be created	`bool`	`true`	no
credentials_path	Path to a service account credentials file with rights to run the Project Factory. If this file is absent Terraform will fall back to Application Default Credentials.	`string`	`""`	no
default_service_account	Project default service account setting: can be one of `delete`, `deprivilege`, `disable`, or `keep`.	`string`	`"disable"`	no
disable_dependent_services	Whether services that are enabled and which depend on this service should also be disabled when this service is destroyed.	`bool`	`true`	no
disable_services_on_destroy	Whether project services will be disabled when the resources are destroyed	`bool`	`true`	no
domain	The domain name (optional).	`string`	`""`	no
enable_shared_vpc_host_project	If this project is a shared VPC host project. If true, you must not set svpc_host_project_id variable. Default is false.	`bool`	`false`	no
folder_id	The ID of a folder to host this project	`string`	`""`	no
grant_services_security_admin_role	Whether or not to grant Kubernetes Engine Service Agent the Security Admin role on the host project so it can manage firewall rules	`bool`	`false`	no
group_name	A group to control the project by being assigned group_role (defaults to project editor)	`string`	`""`	no
group_role	The role to give the controlling group (group_name) over the project (defaults to project editor)	`string`	`"roles/editor"`	no
impersonate_service_account	An optional service account to impersonate. This cannot be used with credentials_path. If this service account is not specified and credentials_path is absent, the module will use Application Default Credentials.	`string`	`""`	no
labels	Map of labels for project	`map(string)`	`{}`	no
lien	Add a lien on the project to prevent accidental deletion	`bool`	`false`	no
name	The name for the project	`string`	n/a	yes
org_id	The organization ID.	`string`	n/a	yes
project_id	The ID to give the project. If not provided, the `name` will be used.	`string`	`""`	no
project_sa_name	Default service account name for the project.	`string`	`"project-service-account"`	no
random_project_id	Adds a suffix of 4 random characters to the `project_id`	`bool`	`false`	no
sa_role	A role to give the default Service Account for the project (defaults to none)	`string`	`""`	no
shared_vpc_subnets	List of subnets fully qualified subnet IDs (ie. projects/$project_id/regions/$region/subnetworks/$subnet_id)	`list(string)`	`[]`	no
svpc_host_project_id	The ID of the host project which hosts the shared VPC	`string`	`""`	no
usage_bucket_name	Name of a GCS bucket to store GCE usage reports in (optional)	`string`	`""`	no
usage_bucket_prefix	Prefix in the GCS bucket to store GCE usage reports in (optional)	`string`	`""`	no
vpc_service_control_attach_enabled	Whether the project will be attached to a VPC Service Control Perimeter	`bool`	`false`	no
vpc_service_control_perimeter_name	The name of a VPC Service Control Perimeter to add the created project to	`string`	`null`	no

Outputs

Name	Description
api_s_account	API service account email
api_s_account_fmt	API service account email formatted for terraform use
budget_name	The name of the budget if created
domain	The organization's domain
enabled_api_identities	Enabled API identities in the project
enabled_apis	Enabled APIs in the project
group_email	The email of the G Suite group with group_name
project_bucket_self_link	Project's bucket selfLink
project_bucket_url	Project's bucket url
project_id	n/a
project_name	n/a
project_number	n/a
service_account_display_name	The display name of the default service account
service_account_email	The email of the default service account
service_account_id	The id of the default service account
service_account_name	The fully-qualified name of the default service account
service_account_unique_id	The unique id of the default service account

Requirements

Software

gcloud sdk >= 269.0.0
jq >= 1.6
Terraform >= 0.13.0
terraform-provider-google plugin >= 3.1, < 4.0
terraform-provider-google-beta plugin >= 3.1, < 4.0
terraform-provider-gsuite plugin 0.1.x if GSuite functionality is desired

`terraform-provider-google` version 2.x

Starting with version 6.3.0 of this module, google_billing_budget resources can now be created. This increases the minimum terraform-provider-google version to 3.1.0

To continue to use a version >= 2.1, < 3.1 of the google provider pin this module to 6.2.1. Or use the core_project_factory submodule directly.

module "project-factory" {
  source  = "terraform-google-modules/project-factory/google"
  version = "~> 6.2.1"
  ...
}

Permissions

In order to execute this module you must have a Service Account with the following roles:

roles/resourcemanager.folderViewer on the folder that you want to create the project in
roles/resourcemanager.organizationViewer on the organization
roles/resourcemanager.projectCreator on the organization
roles/billing.user on the organization
roles/storage.admin on bucket_project
If you are using shared VPC:
- roles/billing.user on the organization
- roles/compute.xpnAdmin on the organization
- roles/compute.networkAdmin on the organization
- roles/browser on the Shared VPC host project
- roles/resourcemanager.projectIamAdmin on the Shared VPC host project

Script Helper

A helper script is included to create the Seed Service Account in the Seed Project, grant the necessary roles to the Seed Service Account, and enable the necessary API's in the Seed Project. Run it as follows:

./helpers/setup-sa.sh -o <organization id> -p <project id> [-b <billing account id>] [-f <folder id>] [-n <service account name>]

In order to execute this script, you must have an account with the following list of permissions:

resourcemanager.organizations.list
resourcemanager.projects.list
billing.accounts.list
iam.serviceAccounts.create
iam.serviceAccountKeys.create
resourcemanager.organizations.setIamPolicy
resourcemanager.projects.setIamPolicy
serviceusage.services.enable on the project
servicemanagement.services.bind on following services:
- cloudresourcemanager.googleapis.com
- cloudbilling.googleapis.com
- iam.googleapis.com
- admin.googleapis.com
- appengine.googleapis.com
billing.accounts.getIamPolicy on a billing account.
billing.accounts.setIamPolicy on a billing account.

Specifying credentials

The Project Factory uses external scripts to perform a few tasks that are not implemented by Terraform providers. Because of this the Project Factory needs a copy of service account credentials to pass to these scripts. Credentials can be provided via two mechanisms:

Explicitly passed to the Project Factory with the credentials_path variable. This approach typically uses the same credentials for the google provider and the Project Factory:

provider "google" {
  credentials = "${file(var.credentials_path)}"
  version = "~> 3.3"
}

module "project-factory" {
  source = "terraform-google-modules/project-factory/google"

  name             = "explicit-credentials"
  credentials_path = "${var.credentials_path}"
  # other variables follow ...
}

Implicitly provided by the Application Default Credentials flow, which typically uses the GOOGLE_APPLICATION_CREDENTIALS environment variable:

# `GOOGLE_APPLICATION_CREDENTIALS` must be set in the environment before Terraform is run.
provider "google" {
  # Terraform will check the `GOOGLE_APPLICATION_CREDENTIALS` variable, so no `credentials`
  # value is needed here.
   version = "~> 3.3"
}

module "project-factory" {
   source = "terraform-google-modules/project-factory/google"

   name = "adc-credentials"
   # Project Factory will also check the `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
   # other variables follow ...
}

APIs

In order to operate the Project Factory, you must activate the following APIs on the base project where the Service Account was created:

Cloud Resource Manager API - cloudresourcemanager.googleapis.com troubleshooting
Cloud Billing API - cloudbilling.googleapis.com troubleshooting
Identity and Access Management API - iam.googleapis.com troubleshooting
Admin SDK - admin.googleapis.com troubleshooting

Optional APIs

Google App Engine Admin API - appengine.googleapis.com troubleshooting
- Please note that if you are deploying an App Engine Flex application, you should not delete the default compute service account (as is default behavior). Please see the troubleshooting doc for more information.
Cloud Billing Budget API - billingbudgets.googleapis.com
- Please note this API is only required if configuring budgets for projects.

Verifying setup

A preconditions checker script is included to verify that all preconditions are met before the Project Factory runs. The script will run automatically if the script dependencies (Python, "google-auth", and "google-api-python-client") are available at runtime. If the dependencies are not met, the precondition checking step will be skipped.

The precondition checker script can be directly invoked before running the project factory:

./helpers/preconditions/preconditions.py \
  --credentials_path "./credentials.json" \
  --billing_account 000000-000000-000000 \
  --org_id 000000000000 \
  --folder_id 000000000000 \
  --shared_vpc 'shared-vpc-host-ed64'

Caveats

Moving projects from org into a folder

There is currently a bug with moving a project which was originally created at the root of the organization into a folder. The bug and workaround is described here, but as a general best practice it is easier to create all projects within folders to start. Moving projects between different folders is supported.

G Suite

The core Project Factory solely deals with GCP APIs and does not integrate G Suite functionality. If you would like certain group-management functionality which was previously included in the Project Factory, see the G Suite module.

Install

Terraform

Be sure you have the correct Terraform version (0.13.0+), you can choose the binary here:

https://releases.hashicorp.com/terraform/

Name		Name	Last commit message	Last commit date
Latest commit History 1,004 Commits
.github		.github
build		build
docs		docs
examples		examples
helpers		helpers
modules		modules
test		test
.gitignore		.gitignore
.kitchen.yml		.kitchen.yml
.pre-commit-config.yaml		.pre-commit-config.yaml
.ruby-version		.ruby-version
CHANGELOG.md		CHANGELOG.md
CODEOWNERS		CODEOWNERS
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
main.tf		main.tf
outputs.tf		outputs.tf
variables.tf		variables.tf
versions.tf		versions.tf

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Google Cloud Project Factory Terraform Module

Compatibility

Upgrading

Usage

Features

Shared VPC subnets and IAM permissions

Inputs

Outputs

Requirements

Software

`terraform-provider-google` version 2.x

Permissions

Script Helper

Specifying credentials

APIs

Optional APIs

Verifying setup

Caveats

Moving projects from org into a folder

G Suite

Install

Terraform

About

Releases

Packages

Languages

License

sanflores/terraform-google-project-factory

Folders and files

Latest commit

History

Repository files navigation

Google Cloud Project Factory Terraform Module

Compatibility

Upgrading

Usage

Features

Shared VPC subnets and IAM permissions

Inputs

Outputs

Requirements

Software

terraform-provider-google version 2.x

Permissions

Script Helper

Specifying credentials

APIs

Optional APIs

Verifying setup

Caveats

Moving projects from org into a folder

G Suite

Install

Terraform

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

`terraform-provider-google` version 2.x

Packages