- when list the available services, it should check the secrets (or configmaps) in the MDC namespaces for the information of available services in the cluster (these secret/configmap will be created at the installation time)
- a service is bound when there is a (configuration) CR exist for a service in another namespace (mobile-app-data). For example, a realm CR will exist for RH-SSO, and a push variant CR will exist for push.
- A bind action will trigger the creation of a (configuration) CR
- A unbind action will trigger the deletion of the CR
- update the tests
|
|
