Developers
Automation recipes
Each recipe combines prerequisites, commands, verification, and rollback.
#Overview
Each recipe combines prerequisites, commands, verification, and rollback.
#Reproducible recipes
A recipe starts with prerequisites and ends with an observable verification. For a static site: list the zone, upload versioned assets, verify URLs, and purge only unversioned paths.
For a network or status agent, create a short key at the last moment, enroll one machine, test one pass, and then install the service. Never reuse an enrollment key as an API token.
#Build an automation
Read identifiers with a
--jsoncommand.Validate files and configuration locally.
Run the mutation and retain its public identifier.
Verify final state and plan one bounded rollback action.
#Verifiable example
cdn-pizza files -z ZONE_ID --json
cdn-pizza upload -z ZONE_ID -f ./dist/app.css
cdn-pizza purge -z ZONE_ID --path /assets/app.css