Cloud Run Function (gen2)
Event-driven or HTTP gen2 function with source upload, dedicated runtime SA and Eventarc trigger wiring.
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 tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-08-03 · 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-function-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-cloud-function/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-cloud-function-1.0.0.sigstore.json \
gcp-cloud-function-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "6a1bd6452e6e732fa6e09915944c570372ebe5ef559a8f9c0bbf279a08005fa3 gcp-cloud-function-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "cloud_function" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-function/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-function?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Cloud Run Function (gen2)](https://www.iac-bazaar.com/catalog/gcp-cloud-function?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "cloud_function" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-function/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-function
A Cloud Run function (gen2) — HTTP or event-driven — with the source zip
uploaded to GCS, a dedicated runtime service account, least-privilege Secret
Manager grants wired automatically, optional Eventarc trigger, VPC egress, and
private invoker IAM. One module call gives you a production function whose
identity is not the default compute service account and whose HTTP surface is
locked down unless you explicitly open it. Works with Terraform and
OpenTofu (>= 1.6), Google provider >= 7.0, < 8.0.
Design & secure defaults
- Dedicated runtime service account (
<name>-fn) — never the default compute SA. Supply your own withcreate_service_account = false. - Private by default: no invoker IAM unless you list
invoker_members;allUsersonly via the explicitallow_unauthenticated = trueopt-in. - Least-privilege secrets:
roles/secretmanager.secretAccessoris granted per referenced secret, not project-wide. Cross-project secrets are left for you to grant where they live. - Content-addressed source: the uploaded object name defaults to
<name>/<md5>.zip, so a changed zip forces a fresh build. - Cost cap:
max_instance_count = 10by default;gen2request concurrency starts at 1 (raise deliberately). - VPC egress via a Serverless VPC Access connector,
PRIVATE_RANGES_ONLYby default.
Requirements
| Requirement | Version |
|---|---|
| Terraform / OpenTofu | >= 1.6 |
hashicorp/google | >= 7.0, < 8.0 |
License
Commercial — LicenseRef-IaCBazaar-Commercial. See the IaC Bazaar terms.
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-run-job
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.
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-function
A Code Engine function in a project created here, callable only from inside the project unless a public URL is accepted by name, with the compute resource token mounted so it obtains IAM tokens through a trusted profile and needs no API key, and CPU, memory, concurrency and execution time capped so a runaway caller cannot drive the bill.
alicloud-fc-function
A Function Compute 3.0 function running as the RAM role you name, with internet access off (on by name), in your VPC when a vpc_config is given, logging every invocation to a Log Service project and logstore (none by name), with code fetched from an OSS object you uploaded. Memory, CPU, disk, timeout and instance concurrency are inputs.