You’ve installed and tested Ansible locally, then installed Ansible AWX (Open Source Ansible Tower) using Docker, and finally tested Ansible AWX with Windows Hosts. You now want to test Azure Provisioning using Ansible AWX.
You want to test Azure Provisioning using Ansible Tower (or the Open Source version, AWX) so you’ll need a way to authenticate with Azure.
Whilst I was working out how to automate Ansible Tower (AWX) using the tower-cli command line tool , I came across an error when trying to create a Job Template using a Microsoft Azure Resource Manager credential, and couldn’t find a solution anywhere online.
After installing Ansible AWX using Docker to test within a Windows environment, I wanted to configure and test Ansible AWX.
After installing Ansible to test within a Windows environment, I wanted to explore other methods of administering and using Ansible other than from the commandline.
For the past year or so I’ve been teaching my friend Steve about the many tools and techniques I’ve been using at work. We gradually built upon each topic until we had a working build for Exchange https://github.com/steevaavoo/ExchangeLab This all worked great as an example, but along the way we ...
A quick tip on how to avoid backup deletion during Velero upgrades via Argo CD.
Myself and several other Microsoft Engineers were recently struggling with intermittent AKS node issues. When the issue occurred, the node(s) would not allow new pods to be created, or any method of connecting a terminal session. In short, there was no method of collecting logs from these broken ...
I had to automate some AKS tasks, which could only continue when disks had detached from their nodes. The solution should accept AKS cluster and PVC names, then wait for the disks to no longer show as Attached, and also be available in both PowerShell and Bash.
Whilst working on a Helm Chart pipeline, I wanted to bring together many of the testing steps I’ve used in other pipelines. This included validation, linting, and installing. The problem was the Helm Chart test pipeline required a nested Kubernetes environment, as our self-hosted GitLab runs on ...
Last week I was tasked with increasing the size of some Persistent Volumes (PV) for one of the apps running on Azure Kubernetes Service (AKS). If possible, this task was to be completed without any downtime to the application.
Popular DevOps tools like Packer and Ansible come with the ability to do interactive debugging, which is essential when troubleshooting issues quickly. However, what happens when you’re running your CI pipelines on Kubernetes?
This post shows how to configure Terraform’s OpenID Connect (OIDC) authentication from GitLab CI to Azure, for both the azurerm provider and the azurerm backend, which until recently was blocked by a known issue. The issue was fixed and released in v1.3.4.
You’ve installed and tested Ansible locally, then installed Ansible AWX (Open Source Ansible Tower) using Docker, and finally tested Ansible AWX with Windows Hosts. You now want to test Azure Provisioning using Ansible AWX.
You want to test Azure Provisioning using Ansible Tower (or the Open Source version, AWX) so you’ll need a way to authenticate with Azure.
Whilst I was working out how to automate Ansible Tower (AWX) using the tower-cli command line tool , I came across an error when trying to create a Job Template using a Microsoft Azure Resource Manager credential, and couldn’t find a solution anywhere online.
This post shows how to configure Terraform’s OpenID Connect (OIDC) authentication from GitLab CI to Azure, for both the azurerm provider and the azurerm backend, which until recently was blocked by a known issue. The issue was fixed and released in v1.3.4.
I needed a way to create all possible combinations from two lists. The first was a list of Azure AD Roles, and the second was a list of target Resource Groups where the AAD Roles should be assigned.
I needed a secure method of configuring Terraform so that plain text passwords were not readable. I also wanted to share the Terraform state with other collaborators, so they could work on the same Terraform configuration.
Troubleshooting “Virtual machine customization failed” error during Terraform vSphere Cloning.
You need to find an MSI Product ID / GUID, but don’t want to install it first.
I wanted to store my PowerShell Modules in VSTS and then install those modules during automated Builds / Release
This quick post covers a gotcha I found using the DSC Package resource. I was having issues installing the Microsoft SQL Server 2012 Native Client (Direct Download http://go.microsoft.com/fwlink/?LinkID=239648&clcid=0x409) like so.
The following error was occurring whilst testing a DSC Configuration “An item with the same key has already been added”
You can get started quickly by using Packer’s simple getting started guide, but you’ll soon want to delve into the documentation for more options and examples. Let’s install it and create our first image!
Before we get into the good stuff, let’s just pause for a moment and remember the “old way” of managing templates.
In the previous post I went over an example Azure DevOps Build Pipeline for PowerShell modules. This post will continue from where we left off and discuss the Azure DevOps Release Pipeline for PowerShell modules.
A few months ago did a demo at the Bristol WinOps Meetup showing an example Azure DevOps Build Pipeline for PowerShell modules. I told everyone I’d get a blog post up “soon” with more information, so here it is; better late than never! I’ll go over the goals for the example PowerShell Module, the...
I wanted to quickly build a vSphere environment so I could test provisioning and configuration with other tools like Terraform and Ansible. I had an old desktop PC lying around with 32GB RAM and several SSDs, so decided to use that.
I always wondered how the default AKS version was selected via the Azure portal, so worked out Bash and PowerShell examples for showing the default AKS version via the command-line.