Automating Deployment of Azure Logic App Using Azure DevOps — Part 2

This is part 2 of a 2 part series where we discuss automating the deployment of an APIM changes as well as automating the Logic Apps deployment which are utilized as backends for the APIM instance.

Part 1 — Automating Deployment of Azure API Management Changes Using Azure DevOps

Part 2 — Automating Deployment of Azure Logic App Using Azure DevOps

In part 1 we discussed in details how to automate deployment of Azure API Management APIs and their configurations from one environment to another. In this post we switch our focus to building CI/CD pipelines for the Logic Apps that serve as backend APIs for the APIM instance. As a reminder Figure 1 and Figure 2 below show both the source and target environments we are dealing with in our scenario. Unlike the case with the APIM the assumption here is that the Maintenance environment doesn’t have any Logic Apps and would have to be created as part of the deployment. Figure 2 below shows the end result after the deployment is completed.

Figure 1: Sandbox Environment (Source Environment)

Figure 2: Maintenance Environment (Target Environment)

When building the CI/CD pipeline for the Logic Apps we had to take couple things into consideration:

• The Logic APPs targets a different SQL server depending on the environment.
• Each SQL Server information is maintained by a connector.
• The connector needs to be deployed in the target environment before the Logic App can be deployed.
• We assume that the SQL database servers are already deployed in both environments.

We start by downloading the Logic App templates as well as the associated connector template from the Azure portal as shown in Figure 1 and Figure 2 respectively.

Figure 1: Downloading the Logic app templates from the Azure Portal

Figure 2: Downloading the Logic app Connector templates from the Azure Portal