Regression/Breaking changes in 0.7.0

[wtrocki]

Different

It looks like sbo binds files by default in openshift console.

0.6.0 release

sh-4.2$ ls /bindings/nodejs-sample-d-ajay-test-akc/
clientsecret user password type clientid

After 0.7.0

 sh-4.2$ ls /bindings/nodejs-sample-d-ajay-test-akc/
KAFKACONNECTION_BOOTSTRAPSERVERS  KAFKACONNECTION_CLIENTSECRET  KAFKACONNECTION_PROVIDER       KAFKACONNECTION_SECURITYPROTOCOL  KAFKACONNECTION_USER
KAFKACONNECTION_CLIENTID          KAFKACONNECTION_PASSWORD      KAFKACONNECTION_SASLMECHANISM  KAFKACONNECTION_TYPE

0.7.0 is not aligned with how spec does it.

[pedjak]

hm, our tests

service-binding-operator/test/acceptance/features/injectBindingsAsFiles.feature

Line 12 in 80e6434

Scenario: Binding is injected as files at the location of SERVICE_BINDING_ROOT env var

verify that the behavior is according to the spec. Can you share you service binding you try to apply?

[wtrocki]

Not sure if service binding is the issue as it is being created by OpenShift Topology as in our summit guides.
Maybe problem is in the spec:

https://github.com/redhat-developer/app-services-operator/blob/main/olm/olm-template/manifests/rhoas-operator.kafkaconnections.crd.yaml#L7-L21

[pedjak]

I can confirm the issue. #949 is going to fix it. Until then, setting spec.namingStrategy: none can work around the issue.