In my previous post, ARM Template Lifecycle Management: DOs and DON’Ts, I recommend to consider YAML for ARM template authoring. In the post, I also suggest using yarm to convert YAML to JSON and/or vice-versa. However, yarm
is not that easy to use because it has to be deployed to Azure or, at least, it has to be run...
Writing ARM Templates in YAML
CICD, JSON, VSTS, ARM Templates, Testing, Pester, Blog, Technology, YAML
Testing ARM Templates with Pester #2 – Azure CLI
Architecture, VSTS, ARM Templates, Azure PowerShell, Testing, Pester, Blog, Technology, Azure CLI
In my previous post, Testing ARM Templates with Pester #1 – PowerShell, I showed how to test behaviours ARM template deployment without actual deployment. At the end of the post, I also briefly mentioned how we can integrate this testing into our CI/CD pipeline. However, I was actually asked many times how I did it on
Azure API Management CI/CD Best Practices
Azure API Management, Continuous Integration, Microsoft, VSTS, ARM Templates, Article, Technology
Introduction
Azure API Management is a great product that we often use on customer solutions. It is an extremely effective way to provide a layer of abstraction between your callers and back-end APIs, and provides centralised governance across your API surface.
However, one of the most common questions from our...
How to automate Project Build numbers in VSTS
CICD, Team City, VSTS, Blog, Technology
If you have migrated over to VSTS (or TFS 2017) from TeamCity, you may have a noticed a useful feature missing.
Now VSTS defaults the build number format to a revision number in the format similar to as shown below.So whats the problem?
This is fine if you are happy with an incrementing number across all projects....