actions/static-site-deploy
Watch
1
0
Fork
You've already forked static-site-deploy
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: coordinate static site deployments through Gandalf
All checks were successful
Test / test (push) Successful in 8s
Details

Browse source
This commit is contained in:
Eric Wendland 2026-07-21 23:26:34 +02:00
commit 411010ef5a
4 changed files with 257 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

13
README.md
View file

@ -45,11 +45,14 @@ jobs:
Only run deployments for trusted branches. A contributor able to change a
workflow that receives production secrets can attempt to expose those secrets.
`purge-endpoint` is optional. The Gandalf-managed gateway reuses the dedicated
Storage Zone password to authorize purging only Pull Zones linked to that
allowlisted zone. It avoids exposing the account-wide Bunny API key to project
repositories. A configured purge is attempted after every non-dry-run sync,
including a retry where Storage already matches the local build.
`purge-endpoint` is the backward-compatible name of the optional Gandalf
deployment gateway input. Before uploading, the action acquires an expiring
per-zone lease. After publishing the manifest, Gandalf verifies its SHA-256
digest, records the revision and deployment outcome, and purges the mapped Pull
Zones only when the manifest changed from the previous successful deployment.
Interrupted uploads are aborted best-effort; abandoned leases expire after 30
minutes. The dedicated Storage Zone password authorizes this workflow without
exposing an account-wide API key to the project.
## Command line