tencent cloud

Serverless Cloud Function

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Related Concepts
How It Works
Strengths
Scenarios
Related Products
Purchase Guide
Billing Overview
Billing Mode
Billable Items and Billing Modes
Function Computing Power Support
Free Tier
SCF Pricing
Billing Example
Payment Overdue
Getting Started
Creating Event Function in Console
User Guide
Quota Management
Managing Functions
Web Function Management
Log Management
Concurrence Management
Trigger Management
Function URL
A Custom Domain Name
Version Management
Alias Management
Permission Management
Running Instance Management
Plugin Management
Managing Monitors and Alarms
Network Configuration
Layer Management
Execution Configuration
Extended Storage Management
DNS Caching Configuration
Resource Managed Mode Management
Near-Offline Resource Hosting Model
Workflow
Triggers
Trigger Overview
Trigger Event Message Structure Summary
API Gateway Trigger
COS Trigger
CLS Trigger
Timer Trigger
CKafka Trigger
Apache Kafka Trigger
MQTT Trigger
Trigger Configuration Description
MPS Trigger
CLB Trigger Description
TencentCloud API Trigger
Development Guide
Basic Concepts
Testing a Function
Environment Variables
Dependency Installation
Using Container Image
Error Types and Retry Policies
Dead Letter Queue
Connecting SCF to Database
Automated Deployment
Cloud Function Status Code
Common Errors and Solutions
Developer Tools
Serverless Web IDE
Calling SDK Across Functions
Third-Party Tools
Code Development
Python
Node.js
Golang
PHP
Java
Custom Runtime
Deploying Image as Function
Web Framework Development
Deploying Framework on Command Line
Quickly Deploying Egg Framework
Quickly Deploying Express Framework
Quickly Deploying Flask Framework
Quickly Deploying Koa Framework
Quickly Deploying Laravel Framework
Quickly Deploying Nest.js Framework
Quickly Deploying Next.js Framework
Quickly Deploying Nuxt.js Framework
Quickly Deploying Django Framework
Use Cases
Overview
Solutions with Tencent Cloud Services
Business Development
TRTC Practices
COS Practices
CKafka Practice
CLS
CLB Practice
MPS
CDN
CDWPG
VOD
SMS
ES
Scheduled Task
Video Processing
Success Stories
Tencent Online Education
Online Video Industry
Tencent Online Education
Best Practice of Tencent IEG Going Global
API Documentation
History
Introduction
API Category
Making API Requests
Other APIs
Namespace APIs
Layer Management APIs
Async Event Management APIs
Trigger APIs
Function APIs
Function and Layer Status Description
Data Types
Error Codes
SDK Documentation
FAQs
General
Web Function
Billing FAQs
Network FAQs
Log FAQs
SCF utility class
Event Handling FAQs
API Gateway Trigger FAQs
Related Agreement
Service Level Agreement
Contact Us
Glossary
DocumentationServerless Cloud FunctionUser GuideWorkflowConfiguration Management

Configuration Management

PDF
Focus Mode
Font Size
Last updated: 2025-12-15 10:54:58
In Configuration Management, you can update the configuration file of the Workflow Controller. The platform provides the capabilities to edit, publish, and roll back configurations.
By customizing the workflow-controller-configmap, you can enable native capabilities supported by open-source Argo Workflows, such as configuring artifacts and archiving workflow status for persistence.

Operation Steps

1. Log in to the Serverless Cloud Function (SCF) console. In the left sidebar, choose Data Engineering > Workflow.
2. On the Workflow page, click the service name to go to the workflow details page.
3. Select Configuration Management. The current workflow-controller-configmap is displayed here. Click Edit Configuration, as shown in the following figure:

4. In the Edit Configuration pop-up window, update the description and configuration content, as shown in the following figure:

Note:
The platform stores the most recent workflow versions that have been published, allowing you to select one for rollback.
5. Click Submit Configuration.
6. After publishing, the platform displays the application status of this configuration and the operation status of Workflow Controller. If the new configuration causes abnormal workflow execution, you can click Rrollback Configuration to restore to a historical version of the configuration.

In the Roll Back Configuration pop-up window, click View Configuration to obtain the specific YAML configuration of a version. This helps you confirm the final configuration file for rollback.

After rollback, the Workflow Controller will immediately restart to apply the selected configuration. This will not affect running workflows, but newly submitted workflows will use the rolled-back configuration.

Scenarios

Configuring Artifacts

By configuring the use of workflow cluster artifacts, you can pass parameters between different steps of a workflow. The output of one step can serve as the input for another, enabling the orchestration of complex workflow steps.
Note:
The key used in artifacts can only be declared as the Custom Key type.

Configuring Workflow Status Archiving for Persistence

Workflow-related resources are periodically cleaned up in the workflow cluster. If you need to analyze or review the workflow execution process, you can configure a persistence policy to store workflows in a database persistently. This allows you to view workflow logs even after the workflow is deleted or the Pods running the workflow are deleted.
Previous Topic: Collecting Event LogsNext Topic: Configuring Access Permissions

Help and Support

Was this page helpful?

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

Feedback