[Feature Request] Externalise the environment.yaml about promptflow HOT 3 CLOSED

Hi @LittleColin thank you for reaching out to us. Let me confirm - your request is:

for now, we will extract secrets (api_key in most cases) and replace them with environment variables only; however, you want us to provide a parameter to customize the fields to be replaced with environment variables.

We will discuss this feature ask first. On the other hand, we haven't done that support before because the configuration can be complicated to specify fields to be replaced, especially given different type of connections may have different fields.

Besides your workaround to add a post-process step:

1. we have a feature that we will respect environment variable of a specific name with a higher priority, then the value in connection yaml
   1. for example, if the connection name is my-connection, you can set an environment variable named MY_CONNECTION_API_BASE and we will respect it on serving.
   2. sorry we haven't mentioned this in current doc, but we have a test for this: link
2. you can also use a CustomConnection and mark all fields you want to replace as secrets - we're hiding all secrets instead of some specific fields.

from promptflow.

Thanks for the response, yes the override appears to work and addresses the feature request. However, the logging could be improved in this area as the myconnection.yaml content is displayed including the api base URL but with no indication that it has been overridden by an environment var. Also, if there's a connection issue, the error does not show the api base that was being connected to (I cannot see anywhere in the logs that the actual api base is emitted).

Suggest changing the cat of myconnection.yaml to indicate value has been overridden by an env var as would be good to know even on a successful connection.

from promptflow.

Thank you for your suggestion. We will use an internal task to track the log improvement and close this issue first.

from promptflow.