You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Purge Bunny CDN cache after successful docs deployment #43
After uploading the docs/site artifact to Bunny Storage, purge the connected CDN Pull Zone automatically so visitors receive the new files without a manual dashboard action.
Acceptance:
Deploy Docs requires BUNNY_API_KEY (account-level API key) and BUNNY_PULL_ZONE_ID (numeric CDN zone ID), retaining BUNNY_ACCESS_KEY for storage uploads.
Purge only after every upload and manifest generation succeed; no purge on upload failure or dry run.
Validate configuration before remote writes; fail visibly on authentication, HTTP, or transport errors; never log the account key or put it in curl arguments.
Update guided GitHub setup, docs, and regression tests; tell the operator exactly which values to configure.
Use the existing deploy-docs-bunny.sh entrypoint so CI filtering in pending #42 already covers the implementation. Build independently from master; do not merge/deploy or change credentials during implementation. Official API: POST https://api.bunny.net/pullzone/{id}/purgeCache with the account AccessKey.
Activity