Version management lets you test, deploy, and roll back configuration changes based on custom request rules.
Use cases
Version management supports canary testing — safely validating configuration changes before production. Typical workflow:
-
Subscribe to the Premium or Enterprise plan and enable version management.
-
Create environments — typically development, staging, and production.
-
Clone an existing version and modify its configuration.
-
Deploy the new version to a test environment, then promote it when ready.
Environments
Use isolated environments to test new configuration versions without impacting live traffic.
After enabling version management, create the environments you need.
Enabling version management automatically creates a default environment that uses Version 0.
The default environment serves as your production environment.
-
Development environment: Isolated environment for testing configuration changes.
-
Staging environment: Mirrors production for validating changes before promotion.
-
Production environment: Serves live user traffic. Uses Version 0 (your website's original configurations) by default. Cannot be edited or deleted.
Clone a version and deploy it to a development environment. After testing, promote it to staging for validation, then to production.
Versions
After you enable version management for a website, the platform dynamically divides your settings into version-specific and global configurations.
Enabling version management automatically creates Version 0.
Version 0 contains your website's current configurations. New environments use Version 0 by default to preserve live traffic.
You cannot create a version from scratch — clone an existing version instead. The clone is an exact copy of the source version's configurations.
Deploy a ready version to a low-priority environment (such as development), then promote it through higher-priority environments until it reaches production.
Features
|
Feature |
Description |
|
Create, edit, and delete environments, and manage deployed versions through upgrades, switches, and rollbacks. |
|
|
After you enable version management for a website, ESA dynamically separates website configurations into versions and global configurations based on the version's feature set. |
Availability by plan
|
Feature |
Free |
Basic |
Standard |
Premium |
Enterprise |
|
Basic version management |
|
|
|
|
|
|
Maximum number of environments |
|
|
|
3 |
10 |
|
Maximum number of versions |
|
|
|
10 |
20 |
Websites on the Premium or Enterprise plan support version management. Cloned version rules count toward your plan's quota.