Search for a command to run...
I used to be a .NET developer. Nowaways, I am a DevOps solutions architect with a focus on Azure and Kubernetes.
I also love productivity topics, especially when it comes to doing more with less of my time. I'm also a daddy, so time is a limited resource for me.
No comments yet. Be the first to comment.
I'm going to share all my secrets with you
Using a pull-request workflow
This is the guide I wish I had
Connecting your GitHub Workflows to Azure AD using OpenID Connect
In this post, I’ll walk through the essentials of configuring an AKS cluster to use Argo CD with an NGINX Ingress Controller. Pre-Requisites You’ll need: An AKS cluster. Here’s a Gist I use to create a simple cluster. Helm 3 Azure CLI A Custom DNS/A...
Azure functions are cute. You can fire up the online function editor from the Azure portal and start hacking away using many languages. In my case, I’d like to start writing some C# and being able to run it and debug it quickly. Eventually, I end up craving Visual Studio & ReSharper along with some unit tests.
Instead of using the Azure Portal, I like to use pre-compiled Azure functions created from Visual Studio
Functions created from the portal are typically “script” functions and they are not compilable. There is no DDL. As you may know, the extension is a .csx.
Today, you can’t deploy your Azure function created in the portal from VSTS. So, they are not as easy to add to your CI/CD pipeline. At this point, I typically start treating my functions like pets and not cattle.
I manually try to deploy a function between environments and paying special attention that the configuration matches between the instances.
All of this applies to Logic Apps too.
This is a is a big no-no for DevOps.
Create an ARM template for your azure function app and its service plan. If you don’t know how to do it, I wrote a blogpost about it.
For the sake of brevity you don’t have to create an ARM template. Be aware that this is still treating your function as a pet :cat: If you choose the dark side, then simply don’t add the Azure Resource Group VSTS task in the release definition.
Provision Build Agent with Azure Functions SDK or use simply use Hosted VS 2017 Build Agent.
Create a new build definition using the ASP.NET build definition template.
Then, if you’re trying this on a new solution, you can simply save and queue this definition.
The release will be the slightly more complex part. It will be very familiar to deploying an App Service.
Start by adding an Azure Resource Group Deployment task to deploy the ARM template that will create the Azure Function Apps and their consumption service plans.
To deploy the function code, for each function app add an App Service deploy task.
You will notice that in the build artifact, there’s a web deploy package for each of the function apps.
Make sure that you’re deploying the right package for the appropriate function app. The web deploy is speficied on the Package or folder field.
Queue it up and give it a go!
