Specification
https://github.com/application-stacks/service-binding-specification

Sample scenarios

• Use specific key in configmap or secret as volume mount
• Use specific key in configmap or secret as volume mount without explicit specification of elementType=string. elementType should default to string
• Use entire configmap or secret as environment variables / volume mounts.
• Use specific string field in a CR , example status.data.host as environment variable or configmap

Acceptance Criteria

1. An OLM descriptor having binding annotations implicitly/explicitly referring to resource paths which have a string value should be bindable end-to-end.
2. The string value could refer to a configmap/secret.
3. Guidance in the annotations associated with use of envVar or volume mount should be taken into account.
4. Guidance in the annotations associated with use of specific "source" keys in the configmap/secret should be taken into account.
5. Use suggested destination binding secret key while building the binding secret.
6. Global or service-specific environment variable prefix needs to be taken into account.
7. Global or service-specific volume mount prefix needs to be taken into account.

Notes

• Work on elementType=sliceOfMaps or elementType=sliceOfStrings can happen in a separate story (APPSVC-529)