Flow Connections for multiple environments

[Chris M3]

How is everyone handling production/sub-production connections when using Flow Designer.  With a code solution, when we build a new integration, we typically build into the code a check against environment and/or a system property.  So for example the code might always use the production connection in production, but we may have the option in a sub-production of using the production connection (For testing purposes) through the system property.

In Flow Designer, you can setup multiple connections for a system, but in the Flow itself, you can't dynamically choose which connection. In my current example, I'm attempting to rebuild a custom Infoblox integration using the Infoblox Spoke.  I've setup a connection to our Production and Lab Environments, but I can't make the flow choose which one to use without duplicating the entire flow.

Is there something we're missing, and if not, how are other teams getting around this issue.

[Albert13]

For something like rest where subprod/prod have different endpoints and creds we have the endponts stored in a system property and use the script to determine what environment we're in.  Same thing with the cred but that property holds a sys_id for the cred record and then it's just a lookup and we can get the username and password

[Chris M3]

Right, this works when you're scripting the interface, but in Flow Designer with connections, there doesn't seem to be a way to dynamically pick the connection.  The defined connection is what it is.

[Albert13]

Are you wanting to use a using a Connection Alias or Define Connection Inline?

[Chris M3]

I'd like to be able to pick between connection alias's inline instead of at development.