Seperate configuration from flow or business logic
If we now have a look at the json file that makes up a Logic app, we can see that throughout the entire file, references are being added to the actual runtime deployment of the various API apps. We also see values for the various connectors in the json structure.
It would really help (in deployment of one flow to various staging slots) to seperate configuration or runtime values from the actual flow logic.
With SDK 2.6 you can now check your Logic Apps into source control, and use different parameter files for each of the different environments, separating runtime config out from the definition itself.
Adrian DeFazio commented
Is there any documentation on how you go about using different parameter files for each of the different environments? It would be good to see how to separate the runtime config from the definition.
Dan Friedman commented
How do we check Logic Apps into source control? I don't see anything here: https://azure.microsoft.com/en-us/documentation/articles/azure-sdk-dotnet-release-notes-2_6/