Managing Application Settings of a Container-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 container mounting path.
Container Mount Path
Absolute path for mounting the configuration file. Example: /tmp.
NOTICE:Do not mount a data volume to a system directory such as / or /var/run. Otherwise, an exception occurs. An empty directory is recommended. If the directory is not empty, ensure that the directory does not contain any file that affects application startup. Otherwise, the files will be replaced, causing application startup exceptions. As a result, the application fails to be created.
- 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.
- 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 container mounting path.
Container Mount Path
Absolute path for mounting the configuration file. Example: /tmp.
NOTICE:Do not mount a data volume to a system directory such as / or /var/run. Otherwise, an exception occurs. An empty directory is recommended. If the directory is not empty, ensure that the directory does not contain any file that affects application startup. Otherwise, the files will be replaced, causing application startup exceptions. As a result, the application fails to be created.
- Click OK.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
