Cloudflare Version Management

Cloudflare Version Management allows you to safely test, deploy, and roll back changes to your zone configuration settings.

​​ Benefits

By using Version Management, you can:

• Create independent versions to make changes with no risk of impacting live traffic.
• Safely deploy changes to staging environments ahead of deploy to production.
• Quickly roll back deployed changes when issues occur.

​​ Availability

For access, enable Zone Versioning in the Cloudflare dashboard.

​​ Limitations

Version Management does not currently support or have limited support for the following products or features:

• Waiting Room
  • Users active on the site may be placed back in the queue.
  • Users in the queue may lose their place in line.
  • Traffic may exceed limits.
• China Network
  • Regardless of the version deployed to production, traffic in China will always target the root zone.
  • Other incompatibility issues with Access and ICP licenses.
• WAF Attack Score
  • WAFML settings are not cloned when a new zone version is created.
• API Shield
  • Some API Shield settings are not cloned when a new zone version is created.
  • Customers are allowed to opt-in to remove the UI block that prevents enabling Version Management.
• Cache
  • Cache settings are versioned, but cache keys are not.
  • Caching a new URL on staging would cache it for production as well.
  • Purging cache on staging would purge it on production too.
  • Promoting a new version to production would wipe all exiting cache.
• Workers Cache API
  • Product incompatibility issues.
  • Workers Cache API does not work with Version Management.
• Cache Rules when used with Cloudflare Images
  • Product incompatibility issues.
  • Image Resizing does not work with additional_cacheable_ports Cache Rule setting and Zone Versioning.
• Domain Scoped Roles
  • Domain Scoped Roles apply only to your root zone.
  • Once a new version is created, these roles do not copy over and they lose access to versions.
• Security Insights
  • Security findings are not shown when Zone Versioning is enabled and the first version is deployed to production.
• Network Error Logging
  • NEL settings are not cloned when a new version is created.
• Wrangler
  • If a version has a worker route, it might disappear when a worker is deployed via Wrangler.
  • If two versions have the same custom domains, the worker might randomly choose between them.
• Cloudflare API Open API docs link
  • Zone Version Management does not currently expose a public API.
  • Customers can only use Version Management through the Cloudflare dashboard.
• Terraform
  • Zone Version Management does not currently support Terraform.
  • Customers should either use Terraform or Version Management.

​​ Requirements

To use Version Management, the following must all be true:

• Your zone is on an Enterprise plan.
• Your zone is in an active state.
• Your zone uses WAF managed rules.
• Your zone has migrated to use Custom Rules instead of Firewall Rules (deprecated).
• Your account uses the new WAF Open external link (if not, contact your account team).
• Your user account must have an API Key provisioned (if not, view your API Key).
• Your user account must have API Access enabled. Refer to control API Access for more information.
• You must use the dashboard to manage versioning.