导航|地址|刷新
Infrastructure as Code (IaC)

Skip to contentDocumentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/workers/llms.txt
Use this file to discover all available pages before exploring further.



DocsDirectoryAPISDKsChangelog

Search

Log in






Workers

/




Overview


Getting started


CLI

Dashboard

Prompting

Templates





Examples

Tutorials


Best practices


Workers Best Practices






Demos and architectures


Overview

Build an Interactive ChatGPT App






Local development


Overview

Environment variables and secrets

Vite Plugin ↗

Choosing between Wrangler & Vite

Developing with multiple Workers

Adding local data

Supported bindings per development mode

Local Explorer

Share a local dev server





Playground


Configuration


Overview


Workers Sites


Overview

Start from existing

Start from scratch

Start from Worker

Workers Sites configuration





Bindings ↗

Compatibility dates

Compatibility flags

Cron Triggers

Environment variables


Integrations


Overview

APIs

External Services





Multipart upload metadata

Page Rules

PlacementBeta


Routes and domains


Overview

Custom Domains

Routes

workers.dev





Secrets






Versions & deployments


Overview

Deployment management

Preview URLs


Gradual deployments


Overview

Version affinity

With Durable Objects





Version overrides

Rollbacks






CI/CD


Overview


Builds


Overview

Configuration

Automatic pull requests


Git integration


Overview

GitHub integration

GitLab integration





Build image

Build caching

Build branches

Build watch paths

Deploy Hooks

Advanced setups

Event subscriptions

Troubleshooting builds

Builds API reference

Limits & pricing

MCP serverMCP






External CI/CD


Overview

GitHub Actions

GitLab CI/CD










Workers Cache


Overview

Configuration

Cache keys

Purging the cache

Examples

Debugging

Limitations






Runtime APIs


Overview


Remote-procedure call (RPC)


Overview

Lifecycle

Reserved Methods

Visibility and Security Model

TypeScript

Error handling






WebAssembly (Wasm)


Overview

Wasm in JavaScript






Bindings (env)


Overview

AI ↗

Analytics Engine ↗

Assets ↗

Browser Run ↗

D1 ↗

Dispatcher (Workers for Platforms) ↗

Durable Objects ↗

Dynamic Worker Loaders

Environment Variables ↗

Hyperdrive ↗

Images ↗

KV ↗

Media Transformations ↗

mTLS

Queues ↗

R2 ↗

Rate Limiting

Secrets ↗

Secrets Store ↗Beta


Service bindings


Overview

HTTP

RPC (WorkerEntrypoint)





Stream ↗

Vectorize ↗

Version metadataBeta

Workflows ↗





Cache

Console

Context (ctx)

Encoding

EventSource

Fetch


Handlers


Overview

Alarm Handler ↗

Email Handler ↗

Fetch Handler

Queue Handler ↗

Scheduled Handler

Tail Handler





Headers

HTMLRewriter

MessageChannel


Node.js compatibility


Overview

assert

AsyncLocalStorage

Buffer

crypto

Diagnostics Channel

dns

EventEmitter

fs

http

https

net

path

process

Streams

StringDecoder

test

timers

tls

url

util

zlib





Performance and timers

Request

Response

Scheduler


Streams


Overview

ReadableStream

ReadableStream BYOBReader

ReadableStream DefaultReader

TransformStream

WritableStream

WritableStream DefaultWriter





TCP sockets

Web Crypto

Web standards

WebSockets






Static Assets


Overview

Get Started

Configuration and Bindings


Routing


Full-stack application

Single Page Application (SPA)

Static Site Generation (SSG) and custom 404 pages

Worker script


Advanced


Gradual rollouts ↗

HTML handling

Serving a subdirectory









Headers

Redirects

Direct Uploads

Billing and Limitations


Migration Guides


Migrate from Pages to Workers

Migrate from Netlify to Workers

Migrate from Vercel to Workers










Framework guides


Deploy an existing project


Web applications


React + Vite

Astro

React Router (formerly Remix)

Next.js

Vue

RedwoodSDK

TanStack Start

Microfrontends

SvelteKit

Vike


More guides...


Analog

Angular

Docusaurus

Gatsby

Hono

Nuxt

Qwik

SolidBeta

Waku










Mobile applications


Expo






APIs


FastAPI ↗

Hono ↗






AI & agents


Agents SDK ↗

LangChain ↗










Databases


Connect to databases

Analytics Engine ↗

Vectorize (vector database) ↗

Cloudflare D1 ↗

Hyperdrive ↗


3rd Party Integrations


Overview

Neon

PlanetScale

Supabase

Turso

Upstash

Xata










Testing


Overview


Vitest integration


Overview

Write your first test

Recipes and examples

Configuration

Test APIs

Isolation and concurrency

Debugging

Known issues


Migration guides


Migrate from Vitest 3 to Vitest 4

Migrate from Miniflare 2's test environments

Migrate from unstable_dev










Integration test harness


Overview

Get started

Configure the test harness

Prepare test state

Interact with Workers

Integrations






Miniflare


Overview

Get Started

Writing tests


Core


Compatibility Dates

Fetch Events

Modules

Multiple Workers

Queues

Scheduled Events

Variables and Secrets

Web Standards

WebSockets






Developing


Attaching a Debugger

Live Reload






Migrations


Migrating from Version 2






Storage


Cache

D1

Durable Objects

KV

R2









Wrangler's unstable_startWorker()






Observability


Overview

Metrics and analytics


Logs


Overview

Workers Logs

Real-time logs

Tail Workers

Workers Logpush






TracesBeta


Overview

Custom spansBeta

Spans and attributes

Known limitations






DevTools


Overview

Breakpoints

Profiling CPU usage

Profiling Memory





Query Builder


Exporting OpenTelemetry Data


Overview

Export to Honeycomb

Export to Grafana Cloud

Export to Axiom

Export to Sentry

Export to PostHog





MCP serverMCP

Errors and exceptions


Integrations


Sentry





Source maps and stack traces






Wrangler


Overview

Install/Update Wrangler


Migrations


Migrate from Wrangler v3 to v4

Migrate from Wrangler v2 to v3


Migrate from Wrangler v1 to v2



Wrangler v1 (legacy)


Overview

Install / Update

Authentication

Commands

Configuration

Webpack





1. Migrate webpack projects

2. Update to Wrangler v2









API


Commands


Overview

Workers

General commands

Artifacts

Browser

Certificates

Containers

D1

Flagship

Hyperdrive

KV

Pages

Pipelines

Queues

R2

Secrets Store

Tunnel

Vectorize

VPC

Workers for Platforms

Workflows





Authentication profiles

Bundling

Configuration

Custom builds

Deprecations

Environments

System environment variables






Vite plugin


Overview

Get started

Tutorial - React SPA with an API


Reference


API

Static Assets

Debugging

Migrating from wrangler dev

Secrets

Vite Environments

Cloudflare Environments

Non-JavaScript modules

Programmatic configuration










Languages


Overview


JavaScript


Overview

Examples ↗






TypeScript


Overview

Examples ↗






Python WorkersBeta


Overview

The Basics

How Python Workers Work

Foreign Function Interface (FFI)

Standard Library

Examples


Packages


Overview

FastAPI

Langchain










RustBeta


Overview

Supported crates










Platform


Overview

Pricing


Changelog


Overview

Workers (Historic)

Wrangler





Limits

Choose a data or storage product

Betas

Deploy to Cloudflare buttons

Claim deployments (temporary accounts)

Built with Cloudflare button

Known issues

Workers for Platforms ↗

Infrastructure as Code (IaC)





Glossary


Reference


How the Cache works

How Workers works

Migrate from Service Workers to ES Modules

Protocols

Security model






Agent resources


Agent setup ↗

Cloudflare Skills ↗

Code Mode MCP Server ↗

Domain-specific MCP Servers ↗MCP

Workers llms.txt ↗

Workers llms-full.txt ↗

Cloudflare Docs llms.txt ↗

Cloudflare Docs llms-full.txt ↗













Home

/Workers

/Platform

/Infrastructure as Code (IaC)



Infrastructure as Code (IaC)


Last updated Apr 23, 2026|Copy as Markdown|View as Markdown|Agent setup

OverviewWorkers BundlingTerraformBindings in Terraform KV Namespace Binding R2 Bucket Binding D1 Database Binding Durable Object Binding Service Binding Queue Binding Vectorize Binding Workers AI Binding Hyperdrive Binding VPC Service Binding Analytics Engine Binding Environment Variables Secret Text Binding Complete ExampleCloudflare API LibrariesCloudflare REST API multipart/form-data upload API Python WorkersConsiderations with Durable ObjectsConsiderations with Worker Versions Resource immutability Module Content Import Behavior Examples




While Wrangler makes it easy to upload and manage Workers, there are times when you need a more programmatic approach. This could involve using Infrastructure as Code (IaC) tools or interacting directly with the Workers API. Examples include build and deploy scripts, CI/CD pipelines, custom developer tools, and automated testing.

To make this easier, Cloudflare provides SDK libraries for popular languages such as cloudflare-typescript ↗ and cloudflare-python ↗. For IaC, you can use tools like HashiCorp's Terraform and the Cloudflare Terraform Provider to manage Workers resources.

Below are examples of deploying a Worker using different tools and languages, along with important considerations for managing Workers with IaC.

All of these examples need an account ID and API token (not Global API key) to work.


Workers Bundling


None of the examples below do Workers Bundling. This is usually done with Wrangler or a tool like esbuild ↗.

Generally, you'd run this bundling step before applying your Terraform plan or using the API for script upload:
wrangler deploy --dry-run --outdir build
When using Wrangler for building and a different method for uploading, make sure to copy all of your config from wrangler.json into your Terraform config or API request. This is especially important with compatibility_date or flags your script relies on.


Terraform


In this example, you need a local file named my-script.mjs with script content similar to the below examples. Learn more about the Cloudflare Terraform Provider, and refer to the Workers script resource example ↗ for all available resource settings.
variable "account_id" { default = "replace_me"}resource "cloudflare_worker" "my_worker" { account_id = var.account_id name = "my-worker" observability = { enabled = true }}resource "cloudflare_worker_version" "my_worker_version" { account_id = var.account_id worker_id = cloudflare_worker.my_worker.id compatibility_date = "2025-02-21" # Set this to today's date main_module = "my-script.mjs" modules = [ { name = "my-script.mjs" content_type = "application/javascript+module" # Replacement (version creation) is triggered whenever this file changes content_file = "my-script.mjs" } ]}resource "cloudflare_workers_deployment" "my_worker_deployment" { account_id = var.account_id script_name = cloudflare_worker.my_worker.name strategy = "percentage" versions = [{ percentage = 100 version_id = cloudflare_worker_version.my_worker_version.id }]}
Notice how you do not have to manage all of these resources in Terraform. For example, you could use just the cloudflare_worker resource and seamlessly use Wrangler or your own deployment tools for Versions or Deployments.


Bindings in Terraform


Bindings allow your Worker to interact with resources on the Cloudflare Developer Platform. In Terraform, bindings are configured differently than in Wrangler. Instead of separate top-level properties for each binding type (like kv_namespaces, r2_buckets, etc.), Terraform uses a single bindings array where each binding has a type property along with type-specific properties.


…(内容过长已截断)

------
导航页 打开网址