-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Support setting properties on a Service Binding connector in Topology view
-
False
-
False
-
To Do
-
0
-
Undefined
-
Not Supported
Description
As a user, I want to configure the properties of my Service Binding connector in the Topology view, so I can, for example, set the the `bindAsFiles`to control how the binding details are injected into my application.
Acceptance Criteria
- Set the `bindAsFiles` property on a Service Binding connector in the Topology view to `true`.
- Have this change reflected in the underlying ServiceBinding CR.
- Observe that the binding details are mounted into the application Pod as files.
- Set the `bindAsFiles` property on the Service Binding Connector in the Topology view back to `false`.
- Have this change reflected in the underlying Service Binding CR.
- Observe that the binding details are set as environment variables in the application.
Additional Details:
This requirement is needed in order to allow a user to configure how the binding details are injected into the application. Quarkus apps for example want to have the binding information mounted into the Pod's filesystem, other languages/frameworks prefer environment variables, so we need to be able to control that configuration.
Note
This has been on the backlog of the "Managed App Services: Developer Experience and Tooling" call for a while: https://docs.google.com/document/d/1-wtXvLDyb9xkLNVtt-e1kJ10bHuuDUa1wkzznJDIlNQ/edit?usp=sharing
- is related to
-
ODC-5947 Support specifying a name for a Service Binding connector in Topology view
- Closed
1.
|
Docs Tracker | Closed | Unassigned | ||
2.
|
QE Tracker | Closed | Unassigned | ||
3.
|
TE Tracker | Closed | Unassigned |