Managing Pullzones for Edge Scripting

Edge Scripts are required to be attached to a Pullzone in order to be executed. Here’s how you can manage this association via Terraform.

Terraform-managed Scripts

If you already have a Pullzone managed via Terraform and you want to attach an Edge Script to it, you’ll need the following attributes on your resource:

Standalone Script
Middleware Script

resource "bunnynet_pullzone" "my-app" {
    name = "my-app"

    origin {
        type   = "ComputeScript"
        url    = "https://bunnycdn.com"
        script = bunnynet_compute_script.my-script.id
    }

    routing {
        filters = ["scripting"]
    }
}

resource "bunnynet_pullzone" "my-app" {
    name = "my-app"

    origin {
        type   = "OriginUrl"
        url    = "https://my-origin.example.com"
        middleware_script = bunnynet_compute_script.my-script.id
    }

    routing {
        filters = ["scripting"]
    }
}

Edge Script created via Dashboard

Edge Scripts created via the bunny.net Dashboard already are attached to a Pullzone, so you need to import it into your Terraform configuration:

Define the resource

resource "bunnynet_pullzone" "my-app" {
    name = "my-app"

    origin {
        type   = "ComputeScript"
        script = bunnynet_compute_script.my-script.id
        url    = "https://bunnycdn.com"
    }

    routing {
        filters = ["scripting"]
    }
}

Import the pullzone

Run terraform import bunnynet_pullozne.my-app PZID, where PZID is the ID of the Pullzone created alongside the Edge Script.

Terraform

Reference

Guides

Terraform-managed Scripts

Edge Script created via Dashboard

​Terraform-managed Scripts

​Edge Script created via Dashboard

Terraform-managed Scripts

Edge Script created via Dashboard