Cloud Scheduler HTTP Cron Job
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.
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-scheduler-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-cloud-scheduler/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-cloud-scheduler-1.0.0.sigstore.json \
gcp-cloud-scheduler-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "160778a9cfea245c3c71f9966c364eaff8cd7e2690b9404a299ee60a762b074c gcp-cloud-scheduler-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "cloud_scheduler" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-scheduler/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-scheduler?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Cloud Scheduler HTTP Cron Job](https://www.iac-bazaar.com/catalog/gcp-cloud-scheduler?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "cloud_scheduler" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-scheduler/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-scheduler
A Cloud Scheduler cron job that calls an HTTP(S) endpoint on a schedule,
with the retry and timeout controls hand-rolled jobs usually skip: a bounded
attempt deadline, a capped exponential-backoff retry policy, and optional
service-account auth (OIDC for Cloud Run / Cloud Functions / IAP, OAuth for
Google APIs). Works with Terraform and OpenTofu (>= 1.6), Google provider
>= 7.0, < 8.0.
Secure defaults:
- When an auth service account is supplied, the scheduler mints a short-lived OIDC/OAuth token per invocation — no static credential in the request.
- The attempt deadline and retry backoff are bounded, so a hung or flapping endpoint can't pin executions open or hammer a downstream forever.
- Cloud Scheduler in a supported region (e.g.
us-central1) no longer needs an App Engine application.
Requirements
| Requirement | Version |
|---|---|
| Terraform / OpenTofu | >= 1.6 |
hashicorp/google | >= 7.0, < 8.0 |
The Cloud Scheduler API (cloudscheduler.googleapis.com) must be enabled.
The auth service account (if used) must be granted invoker permission on the
target endpoint — that grant is target-scoped and stays outside this module.
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-tasks
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.
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.