Managing Application Settings of a VM-Deployed Component

ServiceStage provides configuration management. By creating a unified configuration file, you can fill the system information (such as the IP address, port number, database address, and application name associated with the environment) of the component environment and application in the variables corresponding to the configuration file. This implements multi-environment component release and upgrade with one-time configuration through file mounting.

This section describes how to manage component configuration files.

Binding a Configuration File: Bind the created configuration file to the component. This implements multi-environment component release and upgrade with one-time configuration through file mounting. Create the configuration file in advance. For details, see Creating a Configuration File or Importing a Configuration File.
Editing a Bound Configuration File: Reset the parameters of the configuration file bound to the component.
Unbinding a Bound Configuration File: Unbind a configuration file that is no longer used from the component. Unbinding a configuration file will not delete it. To delete it, see Deleting a Configuration File.

Binding a Configuration File

Choose Application Settings > Add Configuration File.

Set the configuration file parameters by referring to the following table.

Parameter	Description
Group	Group to which the configuration file belongs.
Configuration File Name	Name of the custom configuration file (for example, config.yaml) mounted to the VM mounting path.
VM Mount Path	Relative path for mounting the configuration file. Example: ./config. The upper-level directory is /opt/application/{CAS_INSTANCE_NAME}/{CAS_INSTANCE_VERSION}/{CAS_INSTANCE_ID}, which stores the environment dependency, installation, startup, and stop scripts, and software packages required for component deployment. {CAS_INSTANCE_NAME} is the component instance name. {CAS_INSTANCE_VERSION} is the component instance version. {CAS_INSTANCE_ID} is the component instance ID.

Parameter

Description

Group

Group to which the configuration file belongs.

Configuration File Name

Name of the custom configuration file (for example, config.yaml) mounted to the VM mounting path.

VM Mount Path

Relative path for mounting the configuration file. Example: ./config. The upper-level directory is /opt/application/{CAS_INSTANCE_NAME}/{CAS_INSTANCE_VERSION}/{CAS_INSTANCE_ID}, which stores the environment dependency, installation, startup, and stop scripts, and software packages required for component deployment.

{CAS_INSTANCE_NAME} is the component instance name.
{CAS_INSTANCE_VERSION} is the component instance version.
{CAS_INSTANCE_ID} is the component instance ID.

Click OK.

Editing a Bound Configuration File

Choose Application Settings.
Select the target configuration file in the configuration file list.
Click Edit in the Operation column.