Solution Default Test Configuration
Specifies solution default test configuration. This values are used for the test step of a solution. The default configuration is used for all solutions in the k5-project, as long as there is no solution-specific test configuration for a solution. This has to be done for each new k5-project.
- Use the Configuration Management API or visit the Swagger UI on that URL
- Use
POST
method create solution default configuration for creating the configuration.
Note: You can find the URL for the Configuration Management API by inspecting the route
named
k5-configuration-management
. It can be easily retrieved by
executing
oc get route k5-configuration-management -n <namespace>
,
whereby <namespace>
points to the namespace, where the Solution Hub
is installed. Request Parameters
Parameter | Type | Description |
---|---|---|
configurationName |
path parameter (String) | The name of the configuration:
ssob-integration-test |
runtimeName |
path parameter (String) | The name of the specific k5-project, e.g.
cpd-runtime-default |
data |
body parameter (YAML) | The configuration values (body parameters) |
Configuration Parameters (Body Parameter)
The following table lists the required configurable parameters for the solution default configuration.
Parameter | Description |
---|---|
user.user-alias.default |
Username used for executing the solution's tests (e.g.
dev-test-user ). The test user must exist
or be created in the realm that this k5-project is using. |
user.<test-username e.g. dev-test-user> |
Password used for the specified default user for executing the
solution's tests (e.g. password123 ) |
Examples
Example body parameter for a typical development stage (data):
user-alias:
default: "dev-test-user"
user:
dev-test-user: "password123"
Attention: Any change to the default configuration will only be applied
to the solutions after a new deployment.