Pull zone command to purge cache

I would like the ability to purge a pullzone's cache from the bunny CLI, something like bunny pullzone purgecache. I know there's know there no pullzone subcommand yet, but there's an existent HTTP API for it:

POST https://api.bunny.net/pullzone/{id}/purgeCache

https://bunny.net/docs/api-reference/core/pull-zone/purge-cache

I really like the flow of bunny storage link [zone], it'd be great to have bunny pullzone link [zone] that allows easily running bunny pullzone purgecache on the configured pullzone.

I would use this as part of the deploy flow for my static sites hosted on Bunny.net.

I see there's a bunny site subcommand that calls out to this API already:

cli/packages/cli/src/commands/sites/api.ts

Lines 727 to 738 in 5201580

    
           // Point production at a deploy: retarget the rewrite rule and purge. The rule propagates async, so purge, wait for the edge to serve it, then purge again so nothing stale survives (the header can confirm on a cached response, which is why the second purge is load-bearing). 
        
           export async function promoteDeploy(opts: { 
        
             coreClient: CoreClient; 
        
             state: RemoteSiteState; 
        
             deployId: string; 
        
           }): Promise<void> { 
        
             const { coreClient, state, deployId } = opts; 
        
             const purge = () => 
        
               coreClient.POST("/pullzone/{id}/purgeCache", { 
        
                 params: { path: { id: state.pullZoneId } }, 
        
                 body: {}, 
        
               });

(Related, but I don't see any docs for the bunny sites CLI at https://bunny.net/docs/cli but it seems quite nice and related to what I am rolling on my own.)

@brettchalupa

Hey @brettchalupa

Great questions! And really good to hear you like the link command. Makes it so much easier when working in a project with a library, PZ, script, etc.

I've been meaning to merge Added basic PZ commands #86 as experimental so users can try it out. I just didn't want to merge it and it be forgotten about with no continuous updates. I'm trying to plan now work on the remaining commands to get those in (feat(stream): import #224 , feat(stream): video libraries, directory linking, uploads, and video management #203 and Apps are next, then PZ). However, you can use the CLI to call the purge endpoint with: bunny api POST /pullzone/12345/purgeCache or if you have a tag: bunny api POST /pullzone/12345/purgeCache --body '{"CacheTag":"product-42"}'
bunny sites is not yet released, probably will blog about this next week - it's been in heavy testing by a few users, and is intended to be a CLI only thing for now with the github action, and if it picks up steam, add it to the Dashboard with an API. Feel free to use it and let me know how it goes, and if it's missing anything you'd like that makes your workflow better.

@jamie-at-bunny

@jamie-at-bunny that's awesome about the PZ PR, I didn't notice it. Sounds good about the bunny api command. 👍 I'm using bunny sites for a new website I made today and so far, so good. Really easy and nice to use. Cool to see how it's all wired together with the edge rules and such. I'll close this issue out then, sounds like it'll all on its way. I'll log any bugs if I run into them!

@brettchalupa

@brettchalupa that's awesome to hear! I merged PR #86 so the next release should provide the same pz link experience as every other command.

I'd love to learn a bit more about your use case too, I plan to add the ability to add functions folder support to sites too, so static sites can still by dynamic in places. Feel free to reply here, or email me jamie [at] bunny

@jamie-at-bunny

@jamie-at-bunny right now I am using Bunny CDN to host a handful of static sites. I push each site to a Storage Zone and have a Pull Zone with a custom domain. I push the generated site to the PZ and then bust the cache with this Ruby script that calls out to the bunny CLI:

#!/usr/bin/env ruby
#
# Upload the built ./book to Bunny.net Storage Zone in parallel.
#
# Requires `bunny` CLI and a configured storage, e.g. `bunny storage link my-storage`
# Supports optional `--dry-run` and `--jobs N` args

DRY_RUN = ARGV.include?("--dry-run").freeze
JOBS = (ARGV[ARGV.index("--jobs") + 1].to_i if ARGV.include?("--jobs")) || 8
DIR = "_build".freeze

files = Dir.chdir(DIR) { Dir.glob("**/*").reject { |f| File.directory?(f) } }
queue = Queue.new
files.each { |f| queue << f }

workers = Array.new(JOBS) do
  Thread.new do
    while (f = queue.pop(true) rescue nil)
      command = "bunny storage files upload #{f} --to #{f}"
      if DRY_RUN
        puts "[DRYRUN] " + command
      else
        unless system(command)
          puts "FAILED: #{f}"
        end
      end
    end
  end
end

Dir.chdir(DIR) do
  workers.each(&:join)
end

puts "Clearing cache..."
system("bunny api POST /pullzone/#{PZ_ID}/purgeCache")

So in a lot of ways a less fancy version than the bunny sites functionality that exists with the deploy folders and edge rules.

I also have some sites where I want more robust redirect logic or some dynamic functionality, so I've experimented with using edge scripting middleware. So the functions support would be quite nice, especially if there was an easy way to test that locally while serving the site locally.

But yeah, that's basically my usecase right now: static site hosting with CLI-based deploys from my local machine.

Navigation Menu

Repository navigation

Pull zone command to purge cache #235

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	// Point production at a deploy: retarget the rewrite rule and purge. The rule propagates async, so purge, wait for the edge to serve it, then purge again so nothing stale survives (the header can confirm on a cached response, which is why the second purge is load-bearing).
	export async function promoteDeploy(opts: {
	coreClient: CoreClient;
	state: RemoteSiteState;
	deployId: string;
	}): Promise<void> {
	const { coreClient, state, deployId } = opts;
	const purge = () =>
	coreClient.POST("/pullzone/{id}/purgeCache", {
	params: { path: { id: state.pullZoneId } },
	body: {},
	});

Pull zone command to purge cache #235

Description

Activity

jamie-at-bunny commented on Sep 25, 2026

brettchalupa commented on Sep 25, 2026

jamie-at-bunny commented on Sep 28, 2026

brettchalupa commented on Sep 28, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions