Cloudflare - Features, integrations, alternatives & more
What it does
Cloudflare is a global cache serving files from the closest server location.
How it works
This action connects with Cloudflare using a Global API key and purges the cache in the selected zone. The action can work on changesets - it means that it may only invalidate new or changed files between deployments. It is best to place it at the end of the pipeline after the deployment actions.
Cloudflare Action Features
- It possible to select different purge modes: purge everything, purge files basing on the repository changeset or purge files basing on the filesystem changeset
- It’s possible to exclude paths and file types from transfer using patterns, specific directories and file names
- For changeset based invalidation there is a Requests limit option as invalidation requests can be very expensive, so make sure to set the limit in order to protect your budget. If the number of files to invalidate exceeds that limit, Buddy will purge all files in this distribution instead of invalidating every single file
- It’s possible to create exceptions from excluded paths, directories and filenames
- Input fields: BaseURL supports environment variables
- The action can be configured in YAML mode. See Cloudflare YAML parameters and Cloudflare YAML config example
- Buddy's Cloudflare API is supported
- The action supports conditional execution: it can be run on each execution, only if there are changes in the repository or specific paths since last execution or if an environment variable has a specific value
- Error handling: you can either stop the execution, mark action and pipeline as failed or proceed the execution, mark action as warning and jump to the next action