Solution specific configuration
Its possible to create a solution specific configuration to override the values from the solution default configuration and solution default test configuration.
To manage solution specific configurations the Configuration Management API can be used.
Parameter | Type | Description |
---|---|---|
configurationName |
path parameter (String) | The name of the configuration:
ssob-sdo-values-yaml or
ssob-integration-test |
runtimeName |
path parameter (String) | The name of the specific Solution Envoy, e.g.
cpd-runtime-default |
solutionAcronym |
path parameter (String) | The acronym of a solution, e.g. ORDERS |
data |
body parameter (YAML) | The configration values (Body Parameters, see Solution default configuration and Solution default test configuration) |
Examples:
- Create or change a solution specific configurationThe following example creates or changes the solution configuration of the solution "service1" to
- disable the test support
- use the DEV binding for calling API dependencies
- not support Events
- not expose the internal APIs
runtimeName cpd-runtime-test solutionAcronym service1 configurationName ssob-sdo-values-yaml Request body feature: testSupport: false devBinding: true kafkaEvents: false exposeInternalApi: false
Note: If creating or changing the solution specific configuration not all possibile parameters have to be included in the request body. Only the configuration parameters that are deviating from the solution default configuration should be included. - Create or change a solution specific test configuration
The following example creates or changes the test configuration of the solution "service1" to user "Testuser" with password "password".
runtimeName cpd-runtime-test solutionAcronym service1 configurationName ssob-integration-test Request body user-alias: default: "Testuser" user: Testuser: "Password"
Attention: Every change in the configuration will be applied for the
solution only with a new deployment.