Why Implement Self Service Infrastructure
One of the many concepts of DevOps is the self service aspect of procuring new infrastructure for teams to work with. I think there are a number of ranges that these particular concept can be implemented. It can be from giving people direct access to their organizations cloud provider's dashboard . . .
Manual Azure Function configuration for Application Insights
Your Azure Functions,full stop, need to have telemetry. This post is not here to debate that issue. What I would like to share is a way to stand up your Azure Function, App Service Plan, Storage Account and a Application Insights in a single deployment via Azure Resource Manager.
. . .
Proxies are a nice addition to Azure Functions that give you a subset of features that an application gateway could provide for your function instances. It has request matching capabilities that let you inspect a specific route and send that request to a specific back-end. You can setup matches based on combinations of uri and HTTP method.
. . .
I noticed that the latest revisions of the git installer was showing VSCode as an option to be the git editor. This means for features where you have to work with a commit message or a rebase todo you can use VS Code to do your task.
To enable this all you have to do is add a line under your
[core] node so that you have the following
[core] . . .
When using ARM templates for your deployments you will find your build or your release pipeline in a situation where you need to get some of those generated values from your template or some references from the resources that ARM created in Azure for you.
I have a couple of PowerShell functions that end up getting leveraged in my VSTS Build . . .
I've been working on a new version of dotnetzero (formerly psakezero). This v2 version has a number of changes that were fun to build.
Large refactoring into smaller PowerShell functions
I'm trying out an approach that takes each PowerShell function and places them into their own file. This was for a couple of reasons. One was . . .
Using YAML to define your builds
In a previous post I talked about high-level and somewhat generic approaches to getting your CICD pipeline to be responsible for more than just your builds but also you infrastructure deployment.
Now I'd like to walk though a an actual implementation of a build definition as code using a ASP.NET Core . . .