Some notes about the configurator side car:

<pbraun_> the flow for bind is rougly:
<pbraun_> 1. you create a binding in the Openshift UI
<pbraun_> 2. A special secret is created
<pbraun_> 3. The config operator is notified about that secret and uses the encoded information to create a new variant in UPS
<pbraun_> 4. If that was successful the config-operator then deletes the secret and takes the response from USP to create another secret
<pbraun_> 5. This new secret has special annotations that are required by the mobile-cli to generate mobile-services.json
<pbraun_> when you create another binding it will see that a secret already exists and just update the config object inside that secret
<pbraun_> (which is just a json string)
<pbraun_> the reverse thing happens on unbind
<pbraun_> thats basically it
<pbraun_> what we're currently working on is to make the config operator watch UPS
<pbraun_> so that when it detects that a variant has been deleted in UPS it can trigger the unbind action for the respective binding
<aliok> ok, got it
<aliok> great explanation
<aliok> the annotations variant/android and variant/ios on the secret: where are they currently used? nowhere, right?
<pbraun_> nowhere
<pbraun_> they are intended for the UI
<aliok> ok, all good. gonna change them and move them to mobile client itself. let me have a look at the code and if I can't manage to add those on the client itself, I will ask for your help
<pbraun_> Ok, sorry one thing
<pbraun_> they are actually used in the APB for error handling:
<pbraun_> https://github.com/aerogearcatalog/unifiedpush-apb/blob/master/roles/bind-unifiedpush-apb/tasks/main.yml#L6
<pbraun_> you need to update them there too