How it works
Version Management works through a combination of environments and versions.
(applied manually) V23: Version 2
(promoted from Development) V24: Version 2
(promoted from Staging) Revert: Production (rollback) V1: Version 1
(rolled back due to issues) V2 --> Development Development --> Staging Staging --> Production Production --> Revert state Development { V22 } note right of Development At each level, test then promote the version. end note state Staging { V23 } state Production { V24 } state Revert { V1 } note right of Revert Once promoted into an environment, a version can be rolled back. end note
Environments
An environment is a place to test different versions of your zone configurations.
When you first enable version management, Cloudflare will automatically create three environments for you:
- Development: Meant to validate that changes work correctly. The default traffic filters are that the
cf.zone.namematches your zone name, theEdge Server IPis a specific value, and the request contains a cookie withdevelopment=true. - Staging: Meant to test changes before sending them to Production. The default traffic filters are that the
cf.zone.namematches your zone name and theEdge Server IPis a specific value. - Production: Meant to hold all settings applied to your zone. You cannot edit the traffic filters - which are just that the
cf.zone.nameis equal to your zone’s name - and cannot delete this environment.
When you create a new version, that version will be available to apply to your Development environment (or whatever environment has the lowest rank). Once you test a version in your Development environment, you would promote that version to the Staging environment and - with no issues - then promote it to Production.
To send traffic to specific environments, send requests to that environment that match the pattern specified in its traffic filters.
Versions
A version is a collection of configuration settings related to your zone, such as Firewall Rules, Page Rules, and other optimization settings.
When you first enable version management, Cloudflare will automatically create Version 1 of your zone, which duplicates all existing zone settings. Within each version, you can update settings as needed. These settings are saved automatically.
When your version is ready, you would then test and promote it through various environments until it reaches Production (or whatever your final environment is).
You can create a new version at any time by choosing to Clone an existing version, which automatically copies over configuration settings from an existing version.
Version settings are applied to zone traffic when you when you promote a version to a new environment and then send traffic to that environment that matches the pattern specified in its traffic filters.