How googlecloudplatform/terraform-google-cloud-run works
Project type and purpose
• This is an open-source Terraform module (Infrastructure-as-Code) for provisioning Cloud Run services on GCP.
• Its core responsibilities are:
• Configure domain mappings
• Apply IAM policies (Cloud Run Invoker)
• Optionally wire in VPC Connectors, Cloud SQL, Secret Manager, CMEK, Org-Policies
File-structure analysis
• Top-level:
• main.tf, variables.tf, outputs.tf – the “root” Terraform entrypoint
• modules/… – submodules packaging distinct chunks of functionality:
– secure-cloud-run-core
– secure-cloud-run-security
– secure-serverless-harness
– secure-serverless-net
– job-exec
– service-project-factory
– v2 (parallel versioning)
• examples/… – usage examples invoking the root module with different configurations
• test/… – fixture and integration tests validating module behavior
• build/, docs/, Makefile, CI workflows for linting/testing/releases
README insights
• Enumerates resources created: Cloud Run service, Domain mapping, IAM role bindings
• Highlights optional integrations: VPC Access, Cloud SQL, Secret Manager, CMEK, Custom Domains
• Declares dependencies: Terraform v1.3+, GCP provider, optional beta provider
a. Main components
– Terraform CLI/Workflow (Terraform binary, state, plan/apply)
– Root module (entrypoint)
– Submodules (each implements a slice of functionality)
– GCP APIs/Services:
• Cloud Run
• IAM
• Serverless VPC Access
• Cloud SQL
• Secret Manager
• Cloud DNS / Cloud Domains (for custom-domain mapping)
– Example harness (gcloud/Inspec tests)
b. Relationships & interactions
1. Operator runs terraform init/plan/apply → Terraform CLI reads root module → loads submodules
2. Each submodule issues Terraform blocks → GCP provider calls respective REST APIs
3. Cloud Run submodule provisions service → revision / container image deploy
4. Domain-map submodule provisions custom-domain mapping → DNS verification step
5. IAM submodule binds roles/run.invoker to service account or members list
6. Optional modules: VPC connector attached to revision, Cloud SQL connection annotation, CMEK key referencing KMS
7. Test harness invokes gcloud & Inspec to verify end-state
c. Architectural patterns & design principles
– Module composition: root module delegates to small, focused submodules
– Optionality via variables & count/for-each meta-arguments
– Separation of concerns: security, networking, compute, project-factory each isolated
– Versioning patterns: parallel “v2” modules for incremental API version support
d. Key technologies / frameworks
– Terraform core, GCP Terraform Provider, GCP Beta Provider
– Google Cloud Run, Serverless VPC Access, Cloud SQL, Secret Manager, Cloud DNS, KMS, IAM