I've stumbled across this use-case recently whereby a user required access to a repository within an Azure DevOps project to make contributions. However, to reduce unnecessary exposure to other areas of the project, the permissions needed to be scoped to just a single repository only. The official docs do not cover this topic terribly well so below explains how this can achieved.

In some (probably very rare) cases you will need to disable Hyper-Threading on a virtual machine in Azure. This post explains how to achieve this.

Storing Helm Charts in an Azure Container Registry (ACR) can be beneficial if you also intend to store you container images within the same registry. This allows use of a single artifact store for your products and a single point of reference.

When writing Terraform code for Azure resources, you'll quickly realise there are subtle differences in the API implementations for different resource types.

One important concept when setting up a continuous deployment pipeline is to make sure your deployments happen in the order you would expect them to, in alignment with your repositories commit history.

I've always been a big fan of Cloudflare products as they seem to have a well refined UI that makes interacting with their services so simple to use. They've recently announced a new product, Cloudflare pages in beta.

Hi there. 👋