Azure

So the Golang learning adventure continues! We have our developer environment setup so we’re ready to dive into more Golang code. In this post, I’ll be talking about types and variables in Go. If you’ve used other languages, you may notice as we go through this that Go has some differences in how it uses types compared to other languages. In this article, we’ll be covering: What types are available to us? Assigning values in Go Constants in Go I’ve built a very simple Go file that works with different types in Go which you can view here. Please feel free to clone it, copy/paste it and play around with it. ...

I’ve been wanting to learn Go for a while now. I’ve tried and failed to keep my learning consistent, so I’ve decided to force myself to keep on top of my learning through a couple of avenues: This Blog I’ve set up. This GitHub repo. In that GitHub repo, I’ll be adding content on both Golang itself and building applications with Go that use Azure. I’ll be building this repo up over time, but if you have a particular sample or scenario that you’d like me to create, please feel free to raise an issue. ...

In a previous blog post, I talked about how we can provision an Azure Container App using Bicep and deploying our Bicep template using GitHub Actions. We’ll now turn our attention to updating the images that our Container App uses by building the new image, deploying it to Azure Container registry and then pulling the newly built image from our registry to our Container App. As part of my infrastructure deployment, I defined a container image as part of my Bicep like so: ...

Application uptime is critical for our cloud applications. Using Azure App Service slots, we can implement the Blue/Green deployment pattern to validate that new versions of our application will perform as expected in a production environment, without causing downtime to our existing version of our application. With App Service slots, we can deploy new versions of our container images to our Green slot, run tests against that slot to ensure that everything is working and then direct incoming traffic to our updated container image. ...

Using Bicep, we can deploy and manage all the resources required for our Azure Container Apps. In this post, we’ll write a Bicep template that defines all the infrastructure required for our Container App and deploy it using the AZ CLI. In our Bicep template, we’ll be deploying the following resources: A Log Analytics workspace. Azure Container Registry An Azure Container App Environment A Container App. Before we kick this off, it’s REALLY IMPORTANT to note that Container Apps is currently in preview! That means what I publish in my present might/will change in your future! One example of this is that the namespace that Container Apps currently reside in will be changing in March 2022, as referenced in this GitHub issue (Note to self, update this article!) ...