[BUG] Cannot resolve connection value from OS environments about promptflow HOT 3 OPEN

Hi @firgavin, thanks for reaching us, actually in the #3236 we have a friend raising the similar problem with you, but I didn't reproduce the problem.
If you are using dockerfile exported by 'pf flow build', could you please check the connection file from the output directory? My test output looks like:

And I ran it with docker run -p 8080:8080 -e AZURE_OPEN_AI_CONNECTION_API_KEY=.... name, the flow can return result successfully.

from promptflow.

@brynn-code Thank you for check this issue. I did search through all open issues but somehow missed that particular one. I've noticed that this feature works correctly only with 'flow serve', as you mentioned in #3236. However, I'm curious why it doesn't work similarly for 'flow test' or 'flow run'? In my scenario, I need to use "flow run" with the same connection management in this container.

from promptflow.

At the early stages of design, we introduced this for 'flow serve' is because we'd like user have a more fluent experience when deploying the flow, as it is frustrated if they need to deploy to several region and then create connection for each one, it will be better if they only have to configure environment variables for each deployment.

For the 'flow test' and 'flow run', usually we assuming that user is doing this locally on their machine, they are still authoring the flow, in this case, we encourage user leverage our connection to store api keys, the stored key was encryted, and encryption key was managed by system ( for example, in windows we will store encrytion key to Credential Manager ), and promptflow package itself will not stored the value anywhere.

Please be careful about it, if user remove it manually, then they can't use connection anymore as promptflow can't decrypt existing connections, unless delete the whole sqlite db.

from promptflow.