Help Center/ CodeArts Deploy/ User Guide/ Creating and Deploying an Application with a Blank Template/ Configuring Application Deployment Actions/ Configuring Deployment Actions for File Operations/ Modifying a Configuration File
Updated on 2025-07-03 GMT+08:00
View PDF

Modifying a Configuration File

This action aims to modify the specified content in a file by identifying specific identifiers. The following figure shows the configuration page.

Table 1 Parameters

Parameter

Description

Action Name

Customized action name displayed in the deployment actions Enter 1 to 128 characters. Do not start or end with a space. Use letters, digits, spaces, and these special characters: -_,;:./()

Environment

Select a host cluster as the deployment object.

Absolute Path

Absolute path of the configuration file to modify.

  • Modify a single file, for example, /usr/local/server.config.
  • Modify multiple files, for example, /usr/local/server.config;/usr/local/a.txt.
  • The wildcard character (*) can be used, for example, /usr/local/*.config. However, you cannot separate multiple wildcards using semicolons (;), for example, /usr/local/*.config;/usr/local/*.txt.

Prefix and Suffix

Parameter reference flag. If no prefix or suffix is matched, the configuration file remains unchanged and no error is reported in logs.

Action Control

You can configure whether to enable this setting.

  • Keep running on failure: whether to continue the task even if this action fails.
  • Execute this action with the sudo permission: whether to use the sudo permission to deploy this action.

Configuration Example

To change the service port, perform the following steps:

  1. Open the configuration file and view the content.

    Figure 1 Viewing the configuration file

  2. Change the prefix and suffix. For example, change the prefix to ${ and the suffix to }.
  3. On the Parameters tab, set Name and Default Value.

  4. Save the configuration and deploy the application.
  5. After the deployment is complete, open the configuration file again.

    The value of ${port} is changed to 8080.
    Figure 2 Viewing the configuration file

If you encounter any problem during deployment, see Solutions to Common Problems.