Cloudflare D1 Database

Deploys a Cloudflare D1 serverless SQL database with an optional primary location hint and read replication configuration. The component provisions a single D1 database resource in the specified Cloudflare account and exports the database identifier for use by Workers bindings.

What Gets Created

When you deploy a CloudflareD1Database resource, Planton provisions:

• D1 Database — a cloudflare_d1_database resource in the specified Cloudflare account, with an optional region hint that maps to the Cloudflare primary_location_hint property
• Read Replication (optional) — when readReplication is configured, the database is created with D1 Read Replication (Beta) enabled, placing read-only replicas across multiple regions to reduce global read latency

Prerequisites

• Cloudflare credentials configured via environment variables or Planton provider config
• A Cloudflare account ID with D1 access enabled
• Application-level Sessions API support if enabling read replication — failing to use the D1 Sessions API with replication enabled will cause data consistency errors

Quick Start

Create a file d1-database.yaml:

apiVersion: cloudflare.planton.dev/v1
kind: CloudflareD1Database
metadata:
  name: my-d1-db
  labels:
    planton.dev/provisioner: pulumi
    pulumi.planton.dev/organization: my-org
    pulumi.planton.dev/project: my-project
    pulumi.planton.dev/stack.name: dev.CloudflareD1Database.my-d1-db
spec:
  accountId: 0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d
  databaseName: my-app-db

Deploy:

planton apply -f d1-database.yaml

This creates a D1 database named my-app-db with Cloudflare selecting the default storage region.

Configuration Reference

Required Fields

Optional Fields

Examples

Minimal Database with Default Region

A D1 database where Cloudflare selects the optimal storage location:

apiVersion: cloudflare.planton.dev/v1
kind: CloudflareD1Database
metadata:
  name: analytics-db
  labels:
    planton.dev/provisioner: pulumi
    pulumi.planton.dev/organization: my-org
    pulumi.planton.dev/project: my-project
    pulumi.planton.dev/stack.name: dev.CloudflareD1Database.analytics-db
spec:
  accountId: 0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d
  databaseName: analytics

Database in a Specific Region

A D1 database pinned to Western Europe, useful for GDPR compliance or when your Workers are deployed in that region:

apiVersion: cloudflare.planton.dev/v1
kind: CloudflareD1Database
metadata:
  name: eu-users-db
  labels:
    planton.dev/provisioner: pulumi
    pulumi.planton.dev/organization: my-org
    pulumi.planton.dev/project: my-project
    pulumi.planton.dev/stack.name: prod.CloudflareD1Database.eu-users-db
spec:
  accountId: 0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d
  databaseName: eu-users
  region: weur

Database with Read Replication

A production D1 database in Eastern North America with automatic read replication enabled for lower global read latency. Your application code must use the D1 Sessions API to maintain consistency:

apiVersion: cloudflare.planton.dev/v1
kind: CloudflareD1Database
metadata:
  name: global-app-db
  labels:
    planton.dev/provisioner: pulumi
    pulumi.planton.dev/organization: my-org
    pulumi.planton.dev/project: my-project
    pulumi.planton.dev/stack.name: prod.CloudflareD1Database.global-app-db
spec:
  accountId: 0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d
  databaseName: global-app
  region: enam
  readReplication:
    mode: auto

Stack Outputs

After deployment, the following outputs are available in status.outputs:

Related Components

• CloudflareWorker — Workers bind to D1 databases for query execution; deploy a Worker alongside your D1 database to serve your application
• CloudflareR2Bucket — object storage commonly paired with D1 for storing large blobs while keeping metadata in D1
• CloudflareKvNamespace — key-value storage useful as a caching layer in front of D1 queries