Skip to main content

GCP deployment prerequisites

Before you deploy a client's DigiTrade environment to Google Cloud Platform, your workstation and your GCP account must meet the requirements below.

N
Written by Niyaz

Use this reference before deploying a client's DigiTrade environment to Google Cloud Platform to check the workstation and GCP account requirements. The Setting Up Automation tab contains the Client Billing Information section and deployment setup actions.

Required tools

Install both tools on the machine used for deployment, then verify each tool in a new terminal so the updated PATH is picked up. The official installation guides cover Windows, macOS, and Linux. On Debian or Ubuntu, Terraform can also be installed from HashiCorp's apt repository.

Tool

Purpose

Installation guide

Verification command

Terraform

The infrastructure-as-code tool that defines and provisions the GCP resources.

Terraform installation guide.

terraform version.

Google Cloud SDK (gcloud)

The command-line tool Terraform uses to authenticate with and manage GCP.

Google Cloud SDK installation guide.

gcloud --version.

Authentication

Terraform authenticates to GCP with Application Default Credentials (ADC). After installing the SDK, sign in once with the account that owns the target project. For automated CI/CD, prefer a service account or workload identity federation. ADC is intended for an implementer running the deployment locally.

Command

What it does

gcloud auth application-default login

Opens a browser sign-in and stores credentials that Terraform reads automatically on every run.

Required GCP permissions

The signed-in account must be able to create and bill a new project, enable APIs, and provision resources. The roles below are typical equivalents, so confirm the exact roles with the administrator of the client's GCP organization or billing account.

Capability

Typical role

Create a project

Project Creator (roles/resourcemanager.projectCreator).

Link the project to billing

Billing Account User on the target billing account (roles/billing.user).

Create projects inside an organization (if one is used)

Organization Administrator (roles/resourcemanager.organizationAdmin).

Enable Google Cloud APIs

Service Usage Admin (roles/serviceusage.serviceUsageAdmin).

Delete the project during teardown

Project Deleter or Owner (roles/owner).

Notes

  • The Billing account and GCP Account Email that own the deployment appear in the Client Billing Information section of the Setting Up Automation tab.

  • A missing or insufficient permission usually surfaces early in terraform apply as a failure to create the project, link billing, or enable a service.

Related

Did this answer your question?

Related Articles