Closed pmacik closed 3 years ago
This looks right to me. In scenario one, we have list of strings, and in the latter, we have a list of 'structs'.
@navidsh @Avni-Sharma Scenario 2 was in use by the strimzi proposal. Am I right?
yes @sbose78 Scenario 2 is used in the case of strimzi. Referred https://github.com/redhat-developer/service-binding-operator/issues/352#issue-572380983 for cross-checking
Discussed in the hangout. @pmacik - thanks for bringing this up. Would you be able to please propose a PR for this one?
Discussed in the hangout. @pmacik - thanks for bringing this up. Would you be able to please propose a PR for this one?
Sure, I'll send a PR for this
The binding annotation spec contains option
sliceOfStrings
forelementType
in annotation.However the spec does not tell how it should behave in various situations. The following scenarios suggest the behavior:
Scenario 1:
sliceOfStrings
from arrayGiven a CRD is annotated with service binding annotation using the
sliceOfStrings
element type like in the following snippet:and the respective CR contains the following spec:
when a service binding is created to bind the service CR to an application the application is enriched by the binding with the following env variables:
Scenario 2:
sliceOfStrings
from slice of mapsGiven a CRD is annotated with service binding annotation using the
sliceOfStrings
element type like in the following snippet:and the respective CR contains the following spec:
when a service binding is created to bind the service CR to an application the application is enriched with the following env variables by the binding: