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 PortalFigure 2: Downloading the Logic app Connector templates from the Azure Portal

Figure 3 shows the structure of our Sandbox repository which hosts the templates for the Logic App and its associated connector.

Figure 3: Logic App and Connector Templates hosted in the Sandbox Repo

Figure 4 and Figure 5 show the CI and CD pipelines for the Logic App along with its associated connector. Here both the Sandbox and Maintenance environments have the same CI/CD pipelines and only differ by the templates parameters overrides. Figure 6 shows the template parameters for the Logic app and Figure 7 shows the template parameters for the associated connector.

Figure 4: Logic App CI pipelineFigure 5: Logic App CD pipelineFigure 6: Logic App parametersFigure 7: Logic App Connector parameters

That is all that is required as its a straightforward affair. Figure 8 and Figure 9 show the final CI/CD for the complete solution (both APIM and Logic Apps).

Figure 8: Different CI pipelines for APIM and Logic AppsFigure 9: Different C pipelines for APIM and Logic Apps

Figure 10 shows the final repo structure.

Figure 10: Repository hosting both the APIM and Logic Apps Code