*What*
As we will be creating bindings for each mobile client, we will need to be able to deal with multiple bindings per service.
One option here is to entirely move away from configmaps and instead use a secret as a secret is what is created by default when a binding is created. This secret should be labeled labelled in a specific way, if it cannot be labelled then we may need to continue using configmaps.
*How*
What we need to do here whether we use confgimaps configmaps or secrets is add a label to the configmap that gets created that contains the mobile client id, then when we are building the config view in the UI and from the CLI, we query the API for configmaps filtering on that label.
remove all the excluded services list stuff from the config command.
label names:
- serviceInstanceID
- mobileClientID |
|
