Cloud Run Job (v2)
A Cloud Run v2 Job for batch and run-to-completion workloads with a dedicated runtime service account, auto-wired Secret Manager accessor grants, VPC egress, bounded retries and per-task timeout.
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan test superseded by live test
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o gcp-cloud-run-job-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-cloud-run-job/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-cloud-run-job-1.0.0.sigstore.json \
gcp-cloud-run-job-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "9a6d0a165450313991b4aea9c869f6ecd0485338e06bdc1d96d68ef864cf3248 gcp-cloud-run-job-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "cloud_run_job" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-run-job/gcp"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/gcp-cloud-run-job?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Cloud Run Job (v2)](https://www.iac-bazaar.com/catalog/gcp-cloud-run-job?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "cloud_run_job" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-run-job/gcp"
version = "1.0.0"
}
```Preview:
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
gcp-cloud-run-job
Cloud Run v2 Job — run-to-completion container workloads (batch processing,
database migrations, scheduled/cron tasks) with the security and reliability
wiring hand-rolled configs skip: a dedicated runtime service account (never the
project default compute SA), least-privilege Secret Manager accessor grants on
exactly the secrets the job references, Direct VPC egress or connector support,
a bounded retry count and per-task timeout, and deletion protection on by
default. Works with Terraform and OpenTofu (>= 1.6), Google provider
>= 7.0, < 8.0.
Creating a job defines it but does not run it — execute it on demand
(gcloud run jobs execute <name>) or on a schedule via Cloud Scheduler,
Workflows or Eventarc.
What you get per module call:
- One Cloud Run v2 job with configurable task count and parallelism
- A dedicated runtime service account (or supply your own)
- Plain and Secret-Manager-sourced env vars + secret volume mounts, with the accessor grants wired automatically
- VPC egress (connector or Direct VPC) for reaching private resources
- Bounded
max_retriesandtask_timeout_secondsinstead of unbounded defaults roles/run.invokergrants listing exactly who may execute the job
Requirements
| Requirement | Version |
|---|---|
| Terraform / OpenTofu | >= 1.6 |
hashicorp/google | >= 7.0, < 8.0 |
The Cloud Run Admin API (run.googleapis.com) must be enabled on the project.
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Inputs
- Outputs
Related modules
gcp-static-site
A Cloud Storage bucket serving a static website. Google's own guide notes that objectViewer lets anyone list the bucket, so this module grants legacyObjectReader: read a named file, list nothing. It says plainly that Cloud Storage does not serve your domain over HTTPS, requires you to accept that everything in it is public, and keeps trimmed previous versions as the rollback.
gcp-cloud-function
Event-driven or HTTP gen2 function with source upload, dedicated runtime SA and Eventarc trigger wiring.
gcp-cloud-run-service
Cloud Run v2 service with autoscaling, secret and VPC egress wiring, custom domain and invoker IAM done right.
gcp-app-engine
The application cannot be deleted and its region cannot be changed - destroy removes it from state and nothing else - and the region pins Firestore for the project. Without IAP every service is public on its appspot hostname. The permanent region must be accepted by name, IAP fronts every service unless public is stated, and a disabled serving status is a choice rather than an accident.
ibm-code-engine-app
A Code Engine project and application with managed_domain_mappings local_private, because the field defaults to local_public and an application deployed with no opinion about it answers the world. scale_min_instances is one rather than zero, run_as_user is not root, and a private image without its pull secret is refused - that failure otherwise arrives long after the apply.
oci-container-instances
A container with no health check is restarted only when its process exits, so a deadlocked one stays; containers run as root unless the security context says otherwise; and a public IP on the instance is an internet-facing container with only an NSG in front. Every container gets a check that restarts it and runs non-root on a read-only filesystem; the instance stays private.