Description of problem: ServiceBindingRequest with multiple backing services doesn't show connector in topology. The schema is changing from a single backing service to an array. How reproducible: Steps to Reproduce: 1. Install Service Binding Operator 2. follow example as in https://github.com/redhat-developer/service-binding-operator/tree/master/examples/multiple_services to create SBR with multiple backing services Actual results: No SBR connector shows up in the topology. Expected results: An SBR connector shows up in topology. Additional info: Requires installation of service binding operator with latest schema or for testing simply update the CRD of the service binding request.
Have verified with `0.1.0-251` still operatorHub has `0.0.24-214` so need source manually latest release of SBO with below ``` apiVersion: operators.coreos.com/v1 kind: OperatorSource metadata: name: avni-operators namespace: openshift-marketplace spec: type: appregistry endpoint: https://quay.io/cnr registryNamespace: redhat-developer ``` Verified 4.5 OpenShift Version 4.5.0-0.ci-2020-03-03-204641 Kubernetes Version v1.17.1 Channel stable-4.4 Cluster ID a5d6d68a-e3af-4023-931b-8119f6e639ec API Server https://api.sp82.devcluster.openshift.com:6443
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409