Deployment configuration
Introduction
It's possible to create a deployment-specific configuration to override the settings of the k5-project configuration. This deployment configuration will only apply to the selected project and only overrides the values that are explicitly set in the deployment configuration. So you have the chance to set your default configurations for all projects inside a k5-project and only override certain settings for a certain project.
Manage Solution Configurations
Similar to the k5-project configuration, you have two options to make the settings. The first option is to visit the Solution Hub and navigate to the k5-project that contains the project and then navigate to the project itself. There you find a tab Deployment configurations which shows all configurable settings and also the default values for this project.
The list of configuration parameters is the same as for the k5-project configuration.
For each category listed there you have the option to edit the configuration or create new bindings. The column on the right always shows the current default setting for all projects in this k5-project. So you can easily decide whether to add specific settings or stick with the defaults.
The second option is via a REST API called Configuration Management API ( see API documentation). This API provides a Swagger UI for ease-of-use but you can use the tool of your choice for calling APIs (e.g. cURL, Postman).
As long as not configured otherwise, the default URL where you can find the Configuration Management Swagger UI is built like this:
https://k5-configuration-<namespace>.apps.openshift-cluster.mydomain.cloudThe exact URL can be found within 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 IBM Industry Solutions Workbench is installed (e.g. k5-tools).
Any change to the configuration will only be applied to the project with a new deployment.