Your team is in the process of developing a new application feature, and the infrastructure has to be adapted. The first step is to change a file in your source control system that describes your infrastructure. When the changed definition file is saved in your source control system, it triggers a new build and release. Your new infrastructure is deployed to your test environment, and the whole process to get the new infrastructure deployed took minutes while you only changed a definition file and you did not touch the infrastructure itself.
Continue reading “Infrastructure as Code VSTS”
When testing deployment of resources in release pipelines, the resource groups need to be cleaned after you are done testing the deployment of the resources. In many scenarios you do not want or have no rights to remove the resource group it self. For removing the resources in the resource group you can use the VSTS task clean resources. This tasks removes all resources in a resource group.
When creating reusable ARM templates you have a number of options on how to manage conditional parts in your templates. The smallest conditions can be done by parameters, medium differences can be done by t-shirt sizes and large differences by linked templates. In this blog post I’ll show how to use implement conditions by linked templates.
Continue reading “Conditional parts in ARM Templates”
Protect your data at rest with disk encryption on Linux VMs and deploying them as Infrastructure as Code.
Create known configuration in your ARM templates with T-shirt sizes
A good way of keeping on top of the configurations deployed in your Azure environment can be done by using T-shirt size configurations. T-shirt Sizes are known working configurations for your ARM templates. By using a T-shirt Size you can take away the complexity from the ARM template consumers. A sample of a T-shirt Size can be a Small, Medium of Large offering from a resource.
In this blogpost I want to show how you can use T-shirt Size configuration in an ARM template. The idea is to deploy a website where you hide all the size setting behind a Small, Medium of Large sizing. The consumer only has two parameters to start the deployment:
Continue reading “Creating a T-shirt size ARM template”
Running Azure PowerShell commands in parallel to speed up your deployments
Making better software starts with shortening the time it takes to get feedback. The less time between you start an action and its result, the bigger the chance you will do anything with the feedback. Faster is better!
Continue reading “Parallel deployment with Azure PowerShell VSTS Release Tasks”
Removing deployments with Powershell to solve the ‘DeploymentQuotaExceeded’ error in Azure.
For some time we have been using Visual Studio Team Services Release Manager for our continuous deployments to Azure. Today our Continuous Deployments to Azure Resource Manager came to a halt with the following error:
[error]DeploymentQuotaExceeded: Creating the deployment 'deployModule-0408-0956' would exceed the quota of '800'. The current deployment count is '800', please delete some deployments before creating a new one. Please see http://aka.ms/arm-deploy for usage details.
Unfortunately we had to find out what was going on, before we could do any new deployments. This was very time consuming, because there were only two google hits on the error. They where not very helpful in solving the error.
Continue reading “Deployment limit in Azure Resource Group”