Scott Zelenka05/13/2020, 3:03 PM
. The execution of the Flow includes a step to write data back to a Prod API of an external system. The challenge comes when making iterations to this Flow in development. The external system's Dev instance still triggers our Flow through GraphQL, but is expecting it to write data back to a Dev API. We could update and deploy the Flow to Cloud, but then the
picks up our Dev Flow, rather than our Prod Flow. The only thing I can think of is to have two different Flows deployed on Cloud (one for Prod and another for Dev). But in that case, promoting from Dev to Prod has a bunch of manual steps prone to human error. Interested in the communities thoughts on how you handle deploying multiple versions of the same Flow between Dev and Prod environments, where the configuration between Dev and Prod are different.
Joe Schmid05/13/2020, 3:20 PM
Scott Zelenka05/13/2020, 3:23 PM
Joe Schmid05/13/2020, 3:27 PM
nicholas05/13/2020, 3:28 PM
Tyler Wanner05/13/2020, 3:52 PM