Azure Technical Specs

Overview

• Azure installer
  • Installed components
• Azure Service Deployment
  • Overview Deployment
  • Website Deployment
  • Api Deployment
  • Function Deployment

Azure installer

During the azure extension installation, the installer will initialize a number of components in the the azure environment you provided. The installer will create 3 different resource groups. One for each environment(Development, Staging, and Production) respectively. Each resource group will then have an Api Management Service installed. This installation process can take up to 35 minutes. The Api Management Service is a component needed to deploy and use Api Gateways. It will be shared across all api gateways in the respective resource group. Do not delete it or rename it.

Azure Service Deployment

Azure service deployment process closely mirrors the AWS deployment process, with a few key differences. The deployment flow is described below.

---

Just like AWS deployment, Azure deployment is triggered from the UI when the user selects azure as the type of platform they want to deploy. The service parameters are then sent to the Jenkins container to kick off the service deployment process. Unlike for AWS, Jenkinks does not use the serverless framework to deploy azure services, instead it uses a custom module that interacts with the azure api. This module is responsible for creating, deleting, and updating all azure components. This module is a cli tool installed into the Jenkins container just like the serverless framework.

Website Deployment

During website service deployment, the azure module will create a few services in your azure account:

• Storage Account
• CDN Endpoint
• CDN Account

Api Deployment

During the API service deployment, the azure module will create the following components:

• Storage Account
• App Hosting Plan
• Function App
• Api Gateway

Function Deployment