UDT connections support #93
Conversation
|
|
||
| When there is a `connections` construct in a `Applications.Core/containers` resource definition with source set to a UDT resource's id, | ||
| 1. The UDT should be visible as a dependency in the application graph. | ||
| 2. All of the properties of the UDT that are of numeric or string type should be set as environment variable in the container. The environment variable key would be `CONNECTION_CONN_NAME_VARIABLE_NAME` and value would be the value of varoable. |
There was a problem hiding this comment.
question for @kachawla , @zachcasper
(correct me if I'm mistaken) Currently for existing connections in Containers, we create environment variables for recipe outputs when their types are string/float/int.
We could continue with the same approach for Container->UDT connections.
(I'm bringing this up since I thought I saw an earlier version of Connections PR follow the same approach as existing and maybe there will need to be more work done to get ALL properties in schema to have env variables). So, I'm checking if that is a requirement.
There was a problem hiding this comment.
based on offine discussion and the use case for external service, we are deciding to propogate all properties than just recipe output. @zachcasper @lakshmimsft @kachawla
This document captures the requirements for a connection involving a UDT resource