Some notes from the card:
- display available service integrations
these integrations are part of the serviceclass externalMetadata
- we can look up provisioned service instances with the serviceName label that match
- The service integration should only show up as greyed out if there is a no serviceinstance in your namespace (even though service itself could be in a different namespace) If , it is bound/ enabled should be highlighted and have a (-) symbol tool tip to unbind
If not bound suggest deploying it
- if the service instance is present then the icon should be show up as black and have (+) symbol
When we click the + it should show the binding modal
https://redhat.invisionapp.com/share/3METBQE2D#/screens/278322072
If the service does not have an existing integration, show a (+) next to add it .
- Clicking the (+) should show the binding modal:
https://redhat.invisionapp.com/share/3METBQE2D#/screens/278322072
It should also prefill the parameters it knows about with details from the service instance itself (such as the service name a parameter that keycloak asks for)
- If it is bound/ enabled the icon should be highlighted and have a (-) symbol to unbind and if clicked should go trigger an unbind (same as delete binding link)
This
There is additional work required after the binding instance has been created. It should effectively create a podPreset. Effectively binding and unbinding here should do what the CLI does when it creates or deletes an integration so looking at that command and reproducing the steps would be a good place to start. |
|
