-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
Services declared in a service binding can have the same type, for example one application depending on two PostgreSQL databases. The current naming scheme currently doesn't take that into account.
The current implementation concatenates the runtime.Object type (e.g. Database) with the extracted field from this dependency (e.g. connectionUrl), resulting in an environment variable like DATABASE_CONNECTIONURL.
This should be changed to concatenate the runtime.Object type (e.g. Database) with the manifest name (e.g. db1) then the extracted field from the dependency (e.g. connectionUrl), resulting in an environment variable like DATABASE_DB1_CONNECTIONURL.
Allowing the user to specify per service environment variable prefix; for example, instead of DATABASE_DB1 as prefix to the configuration, a user could configure this specific dependency to be prefixed with PG1, resulting in an environment variable like PG1_CONNECTIONURL instead in the example stated above.
k
- is incorporated by
-
APPSVC-774 Support for flexible/pass-through binding naming strategy
- Closed
- is related to
-
APPSVC-774 Support for flexible/pass-through binding naming strategy
- Closed