Cloudflare Terraform Provider

The cloudflare_waiting_room_event resource allows you to define specific event configurations for a Cloudflare Waiting Room. Events can override various Waiting Room properties (like custom_page_html, session_duration, or queueing_method) while they are active.

To use this resource, you must have the following permissions:

• Waiting Rooms Read
• Waiting Rooms Write

resource "cloudflare_waiting_room_event" "example_waiting_room_event" {
  zone_id = "023e105f4ecef8ad9ca31a8372d0c353"
  waiting_room_id = "699d98642c564d2e855e9661899b7252"
  event_end_time = "2021-09-28T17:00:00.000Z"
  event_start_time = "2021-09-28T15:30:00.000Z"
  name = "production_webinar_event"
  custom_page_html = "{{#waitTimeKnown}} {{waitTime}} mins {{/waitTimeKnown}} {{^waitTimeKnown}} Event is prequeueing / Queue all enabled {{/waitTimeKnown}}"
  description = "Production event - DO NOT MODIFY"
  disable_session_renewal = true
  new_users_per_minute = 200
  prequeue_start_time = "2021-09-28T15:00:00.000Z"
  queueing_method = "random"
  session_duration = 1
  shuffle_at_event_start = true
  suspended = true
  total_active_users = 200
  turnstile_action = "log"
  turnstile_mode = "off"
}

The cloudflare_pages_project resource allows you to manage Cloudflare Pages projects via Terraform. This includes configuring build settings, deployment environments (production and preview), and various service bindings (like KV, D1, R2, etc.).

Important Requirement: If you use a source block configuration (e.g., connecting to GitHub or GitLab), you must first have a connected account in the Cloudflare dashboard. See the Getting Started with Pages documentation for details.

Required Permissions:

• Pages Read
• Pages Write

resource "cloudflare_pages_project" "example_pages_project" {
  account_id = "023e105f4ecef8ad9ca31a8372d0c353"
  name = "my-pages-app"
  production_branch = "main"
  build_config = {
    build_caching = true
    build_command = "npm run build"
    destination_dir = "build"
    root_dir = "/"
    web_analytics_tag = "cee1c73f6e4743d0b5e6bb1a0bcaabcc"
    web_analytics_token = "021e1057c18547eca7b79f2516f06o7x"
  }
  deployment_configs = {
    preview = {
      # ... preview configuration
    }
    production = {
      # ... production configuration
    }
  }
  source = {
    config = {
      deployments_enabled = true
      owner = "my-org"
      owner_id = "12345678"
      path_excludes = ["string"]
      path_includes = ["string"]
      pr_comments_enabled = true
      preview_branch_excludes = ["string"]
      preview_branch_includes = ["string"]
      preview_deployment_setting = "all"
      production_branch = "main"
      production_deployments_enabled = true
      repo_id = "12345678"
      repo_name = "my-repo"
    }
    type = "github"
  }
}

The cloudflare_zero_trust_dns_location resource allows you to configure secure DNS locations within Cloudflare Zero Trust. You can define destination endpoints (DoH, DoT, IPv4, IPv6), specify allowed source networks, and control DNS response TTL capping.

Required Permissions:

• Cloudflare Zero Trust Secure DNS Locations Write
• Zero Trust Read
• Zero Trust Write

resource "cloudflare_zero_trust_dns_location" "example_zero_trust_dns_location" {
  account_id = "699d98642c564d2e855e9661899b7252"
  name = "Austin Office Location"
  client_default = false
  dns_destination_ips_id = "0e4a32c6-6fb8-4858-9296-98f51631e8e6"
  ecs_support = false
  endpoints = {
    doh = {
      enabled = true
      networks = [{
        network = "2001:85a3::/64"
      }]
      require_token = true
    }
    dot = {
      enabled = true
      networks = [{
        network = "2001:85a3::/64"
      }]
    }
    ipv4 = {
      enabled = true
    }
    ipv6 = {
      enabled = true
      networks = [{
        network = "2001:85a3::/64"
      }]
    }
  }
  max_ttl = {
    mode = "override"
    ttl_secs = 3600
  }
  networks = [{
    network = "192.0.2.1/32"
  }]
}

The action attribute defines what happens when the rate limit threshold is met. It is a read-only attribute with the following nested fields:

• mode (String): The action to perform. Available values: simulate, ban, challenge, js_challenge, managed_challenge.
• timeout (Number): The time in seconds during which Cloudflare performs the mitigation. Must be an integer $\ge$ the period.
  • Note: If mode is challenge, managed_challenge, or js_challenge, do not provide this value; Cloudflare uses the zone's Challenge Passage time.
• response (Attributes): A custom response to return.
  • Note: If mode is challenge, managed_challenge, or js_challenge, do not provide this object; Cloudflare uses zone challenge pages.
  • Nested response fields:
    • body (String): The response body (must match content_type).
    • content_type (String): Must be one of text/plain, text/xml, or application/json.