Cloud Tasks Queue
A Cloud Tasks queue with capped dispatch rate and concurrency, a bounded exponential-backoff retry policy, and full Stackdriver logging so failed dispatches are observable rather than silent.
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-tasks-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-cloud-tasks/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-cloud-tasks-1.0.0.sigstore.json \
gcp-cloud-tasks-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "f7cba9a0eb0f216e913157804625c746e7ac745c2d97ea50260b20ac6b74cfb5 gcp-cloud-tasks-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "cloud_tasks" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-tasks/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-tasks?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Cloud Tasks Queue](https://www.iac-bazaar.com/catalog/gcp-cloud-tasks?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "cloud_tasks" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-tasks/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-tasks
A Cloud Tasks queue with the rate-limit and retry controls that keep a
downstream worker from being overwhelmed: a cap on dispatch rate and on in-flight
tasks, a bounded exponential-backoff retry policy, and full Stackdriver logging
so failed dispatches are observable rather than silent. Works with Terraform
and OpenTofu (>= 1.6), Google provider >= 7.0, < 8.0.
Secure defaults:
- Dispatch rate and concurrency are capped (not unlimited) — tune them down to what your worker can absorb.
- Retries are bounded by
max_attempts, so a permanently-failing task does not retry forever. - Operational logging is on at full sampling (
1.0); lower it to cut log volume/cost.
Requirements
| Requirement | Version |
|---|---|
| Terraform / OpenTofu | >= 1.6 |
hashicorp/google | >= 7.0, < 8.0 |
The Cloud Tasks API (cloudtasks.googleapis.com) must be enabled in 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-cloud-scheduler
A Cloud Scheduler cron job that calls an HTTP(S) endpoint on a schedule, with a bounded attempt deadline, capped exponential-backoff retries, and per-invocation OIDC/OAuth service-account auth.
gcp-eventarc
An Eventarc Pub/Sub trigger wired into a self-contained pipeline - a Cloud Run target, a dedicated delivery service account, and the run.invoker and eventReceiver grants Eventarc silently requires.
gcp-pubsub
Topics with schemas, push/pull/BigQuery subscriptions, dead-letter queues and retry policies preconfigured.
aws-mq
deployment_mode defaults to SINGLE_INSTANCE, and Amazon MQ reboots the instance to patch it - so a single broker has planned downtime on AWS's schedule. Active/standby across two AZs, both log streams on, and passwords in a separate variable from users, because a sensitive value cannot be a for_each argument at all.
aws-kinesis-firehose
Without error_output_prefix, records Firehose could not process are written into the same prefix as the ones it could, wrapped in an error envelope that whatever reads the prefix treats as data. Nothing reports it.
huawei-kafka-streaming
A DMS Kafka instance with enable_auto_topic off, because a producer that misspells a topic otherwise creates one: the messages go somewhere real, nothing errors, and nobody consumes them. TLS and SASL are both on, which is what makes the user mean anything; the disk is encrypted at creation; and what happens when the disk fills is a decision you take.