tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
EdgeOne Skill User Guide
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Overview

PDF
Focus Mode
Font Size
Last updated: 2025-04-02 19:07:15
EdgeOne version management allows you to safely test, deploy, and roll back site configurations.
Note:
This feature only supports sites linked to Standard and Enterprise Edition packages.




Supported Modules

The current version management only supports Layer 7 Acceleration Configuration Group and Edge Functions Configuration Group. Once version management is enabled, the Site Acceleration, Rule Engine, and Edge Functions modules will be in Version Management Mode and can only follow version changes, while other configurations under the site will be in Instant Activation Mode.

Feature Value

1. Allows you to create independent versions for configuration management and changes.
2. Provide a testing environment, allowing you to deploy changes to the testing environment for validation before deploying to the production environment, ensuring potential issues and conflicts can be identified in advance.
3. If any unexpected issues arise after deployment, version management also provides the ability to quickly roll back to a previous version, allowing you to quickly restore to a stable configuration and minimize the negative impact on your business.

Relevant Concepts Reference

Version

In version management, a version is the smallest management unit of configuration. You can create independent versions to manage configuration changes.

Configuration Group

Configuration groups are the upper management units of versions. EdgeOne divides different feature modules into different types of configuration groups, such as: Site Acceleration and Rule Engine modules are divided into Layer 7 Acceleration Configuration Group, Edge Functions - Trigger Rules module is divided into Edge Functions Configuration Group, Layer 4 Proxy module is divided into Layer 4 Acceleration Configuration Group, Security Protection module is divided into Security Configuration Group, etc.
Assuming you use both Layer 7 Acceleration and Security Protection features, and two different teams are responsible for operations, dividing into different configuration groups helps your teams manage their respective configurations more conveniently.

Working Mode

Working modes are divided into Instant Activation Mode and Version Management Mode.
Instant Activation Mode means that configuration changes are immediately issued and will affect all production traffic once effective.
Version Management Mode means that configurations must follow version releases to change, and will only affect traffic in the corresponding environment after the version takes effect.
Before enabling version management, all configurations under the site are in Instant Activation Mode; after enabling version management, configurations in the configuration group will be in Version Management Mode, while other configurations under the site will be in Instant Activation Mode.

Environment

After enabling version management, EdgeOne will provide you with a Test Environment and a Production Environment by default.
Test Environment: EdgeOne provides a set of nodes isolated from the production environment as a test environment, allowing you to safely test if the changes in configuration have any issues.
Production Environment: The entire network of EdgeOne nodes serves as the production environment. Once you have verified the configuration in the test environment, you can deploy the changes to the production environment to affect all production traffic.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback