Hands-on Lab — PCD Google Cloud Professional Cloud Developer

Overview

Prerequisites

Steps

1. 1.Provider, project services, naming

   Enable Cloud Run, Artifact Registry, Pub/Sub, and Secret Manager APIs.

   Copy

   terraform {
     required_version = ">= 1.5"
   
     required_providers {
       google = { source = "hashicorp/google", version = "~> 6.0" }
     }
   }
   
   provider "google" {
     project = "your-project-id" # REPLACE
     region  = "us-central1"
   }
   
   locals {
     labels = {
       project    = "certlabpro-pcd"
       managed_by = "terraform"
     }
   }
   
   resource "google_project_service" "run" {
     service            = "run.googleapis.com"
     disable_on_destroy = false
   }
   
   resource "google_project_service" "artifactregistry" {
     service            = "artifactregistry.googleapis.com"
     disable_on_destroy = false
   }
   
   resource "google_project_service" "pubsub" {
     service            = "pubsub.googleapis.com"
     disable_on_destroy = false
   }
   
   resource "google_project_service" "secretmanager" {
     service            = "secretmanager.googleapis.com"
     disable_on_destroy = false
   }

2. 2.Create an Artifact Registry repository for container images

   Provisions:

   • Artifact Registry

   Artifact Registry is GCP's container + package registry — the modern replacement for the deprecated Container Registry (gcr.io). PCD exam tests this push to Artifact Registry → deploy from Artifact Registry pattern as the canonical CI/CD shape.

   We create a regional Docker-format repository. Push to it after terraform apply via:

   gcloud auth configure-docker us-central1-docker.pkg.dev
   docker tag my-app:latest us-central1-docker.pkg.dev/$PROJECT/certlabpro-pcd-images/my-app:latest
   docker push us-central1-docker.pkg.dev/$PROJECT/certlabpro-pcd-images/my-app:latest
   

   Copy

   resource "google_artifact_registry_repository" "images" {
     repository_id = "certlabpro-pcd-images"
     location      = "us-central1"
     format        = "DOCKER"
     description   = "PCD lab Docker images"
   
     labels = local.labels
   
     depends_on = [google_project_service.artifactregistry]
   }

3. 3.Provision a Pub/Sub topic + subscription (the async backbone)

   Provisions:

   • Pub/Sub

   Pub/Sub is GCP's managed messaging — the foundation of every PCD-pattern event-driven app. Topics are publish-targets; subscriptions are consumer endpoints (pull or push). PCD exam tests at-least-once delivery + idempotent consumers as the load-bearing semantics.

   We create:

   1. A topic orders — where producers publish.
   2. A pull subscription orders-worker — consumers pull from this. Production deployments often use push subscriptions to Cloud Run endpoints instead (the PCD-canonical event-driven shape: Pub/Sub push → Cloud Run); we stay pull here to keep IAM simpler.

   ack_deadline_seconds = 60 gives consumers 60 seconds to ack; longer than the Cloud Run default request timeout and a recurring PCD exam tuning knob.

   Copy

   resource "google_pubsub_topic" "orders" {
     name = "orders"
   
     labels = local.labels
   
     depends_on = [google_project_service.pubsub]
   }
   
   resource "google_pubsub_subscription" "orders_worker" {
     name  = "orders-worker"
     topic = google_pubsub_topic.orders.id
   
     ack_deadline_seconds       = 60
     message_retention_duration = "604800s" # 7 days (max)
   
     retry_policy {
       minimum_backoff = "10s"
       maximum_backoff = "600s"
     }
   
     labels = local.labels
   }

4. 4.Deploy a Cloud Run service with a least-privilege service account

   Provisions:

   • Cloud Run

   Cloud Run is GCP's container-as-a-service — runs Docker containers on Google's serverless infra, scales to zero. PCD-recommended pattern: each Cloud Run service runs as its own service account, never the default Compute service account.

   We deploy a service running the public hello image as a placeholder, attach a per-service service account with roles/pubsub.subscriber on the topic from Step 3, and grant roles/run.invoker to allUsers for unauthenticated access. Switch to IAM-gated invoker for production — the PCD exam tests this allUsers ↔ specific-identity flip.

   Copy

   resource "google_service_account" "worker" {
     account_id   = "certlabpro-pcd-worker"
     display_name = "PCD lab Cloud Run worker"
   }
   
   resource "google_pubsub_subscription_iam_member" "worker_subscriber" {
     subscription = google_pubsub_subscription.orders_worker.name
     role         = "roles/pubsub.subscriber"
     member       = "serviceAccount:${google_service_account.worker.email}"
   }
   
   resource "google_cloud_run_v2_service" "worker" {
     name     = "certlabpro-pcd-worker"
     location = "us-central1"
   
     template {
       service_account = google_service_account.worker.email
   
       scaling {
         min_instance_count = 0 # scale-to-zero — no idle billing
         max_instance_count = 5
       }
   
       containers {
         image = "us-docker.pkg.dev/cloudrun/container/hello"
   
         resources {
           limits = {
             cpu    = "1"
             memory = "512Mi"
           }
         }
       }
     }
   
     labels = local.labels
   
     depends_on = [google_project_service.run]
   }
   
   resource "google_cloud_run_v2_service_iam_member" "public_invoker" {
     name     = google_cloud_run_v2_service.worker.name
     location = google_cloud_run_v2_service.worker.location
     role     = "roles/run.invoker"
     member   = "allUsers" # lab-only; production = specific identity
   }

5. 5.Store app credentials in Secret Manager + grant Cloud Run read access

   Provisions:

   • Secret Manager

   Secret Manager is GCP's secret store — versioned values, IAM-controlled access, automatic rotation hooks. PCD-recommended pattern: app config that's not a secret goes in env vars; app config that is a secret (API keys, DB passwords, OAuth tokens) goes in Secret Manager, referenced by the Cloud Run service.

   We create a secret + initial version, then grant the Cloud Run service account from Step 4 roles/secretmanager.secretAccessor on it. To wire the secret into Cloud Run as an env var, you'd add a env { name = "..."; value_source { secret_key_ref { ... } } } block in the service template (deliberately omitted to keep this step focused).

   Copy

   resource "google_secret_manager_secret" "db_password" {
     secret_id = "certlabpro-pcd-db-password"
   
     replication {
       auto {}
     }
   
     labels = local.labels
   
     depends_on = [google_project_service.secretmanager]
   }
   
   resource "google_secret_manager_secret_version" "db_password_v1" {
     secret      = google_secret_manager_secret.db_password.id
     secret_data = "lab-placeholder-rotate-me"
   }
   
   resource "google_secret_manager_secret_iam_member" "worker_reader" {
     secret_id = google_secret_manager_secret.db_password.id
     role      = "roles/secretmanager.secretAccessor"
     member    = "serviceAccount:${google_service_account.worker.email}"
   }

Cleanup