Manage bindings
Application Composition Projects don't have a global configuration. Instead, configuration can be made for each deployment target that has been added to the project. That allows you to adjust everything individually to match the requirements of each single deployment target.
Besides adding and removing components, you need to configure the bindings of each component in case they make use of any type of bindings.
Configuring the bindings for the components needs to be done for each of the deployment targets you set up.
Configuring bindings
Bindings are a way to configure the connection of components to other resources, e.g., external REST APIs or messaging. To edit these bindings you can use the cogwheel icon next to the "Commit" button. This lets you choose between the following bindings:
- API bindings: used to store information required to call external REST APIs (e.g., URL, certificates, token, etc.)
- Event topic bindings: used to store information on the event topic used for messaging
The configuration of these bindings will only apply for the currently selected deployment target. The bindings need to be configured for each component on each deployment target.
If the component repository that the component was added from is deleted then you will need to remove the component and add it again after selecting the component repository that it is in
Configuring API bindings
Whenever a component has been designed to make use of an API binding this binding needs to get configured. You can find out if you need to configure API binding(s) by clicking on the additional actions part of the "Add component" dropdown button on one of the deployment targets. Clicking on the "Configure API bindings" entry opens a dialog that lists all API bindings used by the components in this deployment target. This allows you to go through this list and configure all API bindings so all components can work as expected when deployed.
You can edit each of these bindings by clicking on the three-dots menu on right side of each table row and clicking on the "Edit" button.
Read more about API bindings.
Configuring topic bindings
Similar to the API bindings every topic binding used by any of the components needs to get configured. You can find out if you need to configure topic binding(s) by clicking on the additional actions part of the "Add component" dropdown button on one of the deployment targets. Clicking on the "Configure topic bindings" entry opens a dialog that lists all topic bindings used by the components in this deployment target.
You can edit each of these bindings by clicking on the three-dots menu on right side of each table row and clicking on the "Edit" button.
Read more about event topic bindings.
Configuring k8s secrets
This configurations are also located in the deployment target's menu bar above the components. To open the settings, click on the additional actions part of the Add component dropdown button and select "Configure Secrets". This will open the "Configure Secrets" dialog that lists all k8s secrets used by application project for this deployment target.
You can create new secrets by using the "Create" button and edit each existing secret by clicking on the three-dots menu on right side of each table row and clicking on the "Edit" button in order to configure the application project. Any created secret here will only apply on the selected deployment target. It will not affect any other usages of this application project on other deployment targets.
Please note that the chosen secret name needs to be unique in the deployment target, so we recommend including the application acronym in the name.