Configuration parameters allow applications to be dynamic, flexible, and environment-specific. They enable managing variables and values that change across deployment environments (e.g., Development, QA, Production), without requiring hardcoded updates. This feature is particularly valuable for managing sensitive information, environment-specific settings, and configurations for integrations.
null
or undefined, in which case the configuration parameter is used.officeEmail
value
officeEmail@office.com
baseUrl
environment variable
BASE_URL
(name convention pointing to an externally defined value)Key | Type | Value | Description |
---|---|---|---|
baseUrl | environment variable | BASE_URL | A reference to the base URL configured externally by DevOps. |
Environment | External Variable Name | Actual Value |
---|---|---|
Development | BASE_URL | https://dev.example.com/api |
QA | BASE_URL | https://qa.example.com/api |
Production | BASE_URL | https://api.example.com |
dbPassword
secret environment variable
DB_PASSWORD
value
, environment variable
, or secret environment variable
.value
: Enter the static value.environment variable
or secret environment variable
: Enter the agreed name convention.ENV
/ENV_SECRET
) are managed by DevOps.processInstanceId
). Avoid using reserved keys for custom configurations.null
or undefined
process variables will default to the corresponding configuration parameter’s value during runtime.