Runtime Configuration and Environment Variables

Administrators can view and modify supported ems.yaml settings through APIs while preserving comments in the original file. Environment variables can also override settings for batch deployment.

Identify configuration sources

Query results provide file values, runtime values, override sources, and editability:

Field	Purpose
value	Value saved in the file; sensitive settings are masked
runtimeValue	Value in the current process
effectiveSource / envName	Whether an environment variable overrides the value, and its name
editable	Whether modification through the configuration API is currently permitted

Settings overridden by environment variables cannot be changed through the page or configuration API. Adjust the variable in the deployment environment and restart as required.

How changes take effect

Settings may take effect immediately, require a restart, or only be written to the file. Follow the API metadata and response messages. A changed runtime value does not necessarily mean startup resources, such as connection pools or directories, have been recreated.

A sensitive value’s mask is not the actual credential; do not submit the mask as a new value.

Integration APIs

Query with GET /ems-yaml-config/list. Submit {"values":{"<configuration-key>":"<new-value>"}} to POST /ems-yaml-config/update. Both require administrator privileges.

Before adjusting storage settings, see Capacity and retention policies. For restoration, see Maintenance freeze.