Recently, I’ve been toying with a small personal side project where I wanted to implement automated release management with a press of a button, including version numbering and uploading build artifacts. In this blog post I’ll outline how this approach could be used in other projects, too.
In the previous posts we’ve covered how to create an Azure Key Vault using Bicep and how to create an Azure Function App using Bicep. Now, let’s see how we can combine them together and reference secrets from a Key Vault in an Azure Function.
I’ve been recently working with some twenty plus Azure Function Apps that I need to manage. Previously, those functions had been handcrafted and managed manually from the Azure portal. In this post I will share how I switched to using Bicep templates instead and what I learned in the process.
Sometimes your Azure DevOps pipelines need to adapt to different situations with sane default values. On the other hand, optional arguments become especially handy when you want to create flexible and reusable templates.
Since Docker announced that the licensing terms for Docker Desktop have changed so that large companies need to start paying there has been growing interest towards alternatives. How can you switch to a free and open source solution, or should you?
An important part of a CI pipeline is to keep you updated on what’s happening. When a build or a test suite fails you might want to be notified about it. In this post we’ll learn how to send messages to a Teams channel from an Azure DevOps pipeline.
Has your API key changed? Maybe you need to update a TLS certificate? There are many reasons why you’d want to edit secrets in Kubernetes. Luckily, this is relatively simple.
Over the years we have seen many tools that enable communication with computer systems using a chat interface. Many of them are now obsolete as their development has ceased, though they still seem to be recommended everywhere. What are the tools that you should use today?