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]

If I understand the ask right

1: Script: get the sys_id of the of dev/test/prod Alias sys_id based on what env you're in

2: Look up to sys_alias

3: Rest step using output of step 2

[Chris M3]

I'm aware it can be done easily that way.

In an OOB Action/Spoke, for example Infoblox, the connection it will use is defined in the Flow - Configure Connections screen, which does not provide an option for scripting.

Or in the Active Directory actions, in the Advanced Options section, again no script options. (Service Now isn't even consistent with how a connection is chosen)

[Albert13]

I see what you mean now, yea.  Don't think you will be able to script it to make it dynamic without building something of your own