DevOps

In this episode, we’re going to be taking a slight detour away from GitHub actions and focus on some of the announcements from GitHub universe last week. We’re going to explore them both from the announcements, and also take a look at some of those features that have already been released. Stay tuned!

You have your .NET Core code. You have your application infrastructure ready. Now, it’s time for us to deploy that application to Azure using GitHub Actions!

Have an application that you want to deploy to Azure in an automated way? Well, before we deploy the application code, we need some Azure Infrastructure for it to run on. In this video, we have you covered on how to deploy that infrastructure!

Want to find out more about how GitHub Actions work? How about the Azure Actions that you might use in your first deployments in the platform? Then stick around, because this video is the one for you!

Want to automate your application deployments into Azure? Heard about Git, GitHub or GitHub actions want to find out more? I’m starting a new series on how you can use GitHub Actions to deploy your applications into Azure! Interested? Then stick around to find out more.

Recently, I’ve been doing a bit of work with GitHub Actions as well as Terraform for a pet project I’ve been working on. I’ve been building a multi-tenanted inventory app for my Yu-Gi-Oh card collection. In this session, we’ll explore some of the GitHub actions that I have used to deploy the application content and various Microservices.

In this episode, we get back to a requirements based topic, and an area that will significantly impact the design of our resulting solution architecture. That topic is security! It’s one of the hot topics that organisations want to discuss when moving to the cloud. So I’m pleased to be joined in this episode by another colleague, Andrew Nathan, who has a wealth of knowledge in the cyber security space.

In this episode, I’m very fortunate to have my first guest come and join me! And what better way to kick this off, than a topic area which is very close to my own heart - DevOps. I’m very excited that I was able to invite Abel Wang, Principal Developer Advocate and DevOps lead to come and join me to talk of his experiences at Microsoft. We jump through a few different areas, from What is DevOps, how it links back to requirements, Data DevOps and shifting left. There’s plenty to learn from in this one, so let’s dive straight in!

In my spare time, I work on a pet project called Theatreers. The aim of this is a microservice based platform focused on Theatre / Musical Theatre (bringing a few of my passion areas together). I’ve recently re-architected the project to align to a multi-region serverless technology stack.

Consider this scenario. You are managing a software project using Azure DevOps, and you have multiple teams working towards a common cadence. Perhaps that cadence is managed by a central team. To gain the most value from your sprint planning, you would need to associate the iterations from the project level with each individual team. This is a scenario that I have for my fictitious Theatreers project, but also a scenario I encountered recently with a colleague. I have been helping them setup an Azure DevOps project to track the development of IP and collateral, so that they can more accurately forecast what they expect to land and show the value being delivered by the team.