Serverless – Continous deployment with GIT [3.1]

This post is one in the cycle of posts related to serverless topic. To check all of them go to serverless category.

In this part I will show you how easy is to connect our function stored in GIT repository to Azure cloud, with continous deployment after every commit.

Repository and Function App

At the beginning you need to create repository to connect it to remote function app. In this step GIT repository is not fully required – you can connect Azure function to storages like OneDrive or Dropbox but it is easier to show you how the changes occur in our code, when it stays on GitHub (public repo FTW). You can check my code on – this is the same code from previous scenario, only published to GH.

Then you need to create you Function App in Azure portal. Find “function app” and choose parameters:

  • App name – Name of group of your functions (in my case Azure-Function-Poc).
  • Subsciption – Which subscription will take costs of this Function App.
  • Resource group – choose how would you like to group tour resources.
  • Hosting plan – You can choose from charging from every Function App or gather it together inside one App Service Plan. I have chosen simple charging.
  • Storage – function needs to be storage in some Azure Storage account. We can either create it or use existing one. I create new azurefunctionpoc

You don’t need to add Azure Insight. After clicking Create, in a moment you will got your function.

Deployment from GitHub

After creation you go inside the function and choose option to setup the deployment: tab Platform features -> CODE DEPLOYMENT section -> Deployment option.

Then you go through Setup, you choose GitHub, authenticate with this provider and check repository and branch you want to connecto to Function App.

You get the window about creation the package and in the moment you get confirmation message:

After these steps you should got your function in Azure portal:

Configuration in Azure

With such deplyment you don’t need to change any option in your Function App – everything will work from the beginning. Parameters as AzureWebJobsStorage are automatically set with connection string to your remote Azure Storage, which was provider during creation of app.

You can check your settings in Function App -> Platfom Features tab -> GENERAL SETTINGS section -> Application settings -> App settings section -> AzureWebJobsStorage.

Testing remote Function App

You can add some file to check whether your function is working. To remote Azure Storage you can drag any file and in function Logs you can check how function is responding to new file (clik to open).

As you can see, function is responding to the new file in blob, describing name and size in log window in function panel.