// DevOps

In a couple of previous blog posts, I provided a writeup on the GitHub Projects Beta. I wrote two posts on automation within GitHub Projects (Adding Issues to GitHub Projects with GitHub Actions for a user profile and Adding Issues to GitHub Projects with GitHub Actions for an Organization profile). I'm pleased to say that the capabilities went Generally Available last week! As a result of the GA announcement and resulting changes, I need to post updates to my older samples.

GitHub is one of my passion areas. You may have realised that already, with the amount of content that I've written about it. That's only going to continue, because I've recently been hired there as an Enterprise Advocate. I've been supporting customers in their DevOps journey for the past 9 years or so. Interestingly, there are some reoccurring themes that I've found that are common. One of those themes is that DevOps is an App Development concept. In fact, it's something that can be applied across domains (e.g. Infrastructure, Data, etc.) This is the start of a new blog series that will address those common themes, particularly in the context of GitHub.

Chris and Matt set up federated identity credentials (OIDC) for passwordless GitHub Actions authentication to Azure, deploy container apps via CI/CD, and discuss workflow trigger strategies for container image deployments.

Chris and Matt debug deployment issues in Azure Container Apps, restructure their Bicep infrastructure as code into separate lifecycles, and configure Dapr state store components backed by Azure Storage.

Chris is the blogger, podcaster, host and producer of his content platform CloudWithChris.com. He uses GitHub to manage, develop, build and deploy it. In this session, Chris explores how GitHub is more than just a Git repository, and how he uses it for his own work: GitHub Issues / Projects to plan the content (Blog & Podcast) backlog GitHub repositories to version control the website's source code (and recently open sourced the theme) GitHub Codespaces to make changes to the site from any device GitHub actions to build/deploy the site, and publish podcast mp3 files

Chris and Matt deploy their containerized microservices to Azure Container Apps for the first time, pulling images from GitHub Packages and exploring the Dapr, KEDA, and Envoy integrations that Container Apps provides.

Your monthly digest covering a packed May 2022 — headlined by Microsoft Build! In this episode, Chris walks through Azure Container Apps going generally available (and why it's one to watch), the limited access preview of Azure OpenAI Service with GPT-3 and Codex models, Azure DNS Private Resolver for hybrid name resolution, Open Service Mesh extension for Azure Arc GA, NGINX natively integrated on Azure, AKS host process containers in preview, Azure Communication Services Email GA, hierarchical partition keys in Cosmos DB, and much more. Plus GitHub and Azure DevOps highlights from a very busy month for the developer ecosystem.

Chris and Matt containerize their Go microservices by writing Dockerfiles, building images, and publishing them to GitHub Packages container registry using GitHub Actions workflows with GITHUB_TOKEN authentication.

GitHub recently posted about a new GitHub Action that can be used to summarise your test results. The action is called test-summary/action, available at github.com/test-summary/action. There are several examples on how to use the action at github.com/test-summary/examples. However, there were no examples on how to use this with Go. I contributed a pull request which showed how to achieve this. In this post, I will show how to use the action with Go.

Have you heard about the term Developer Velocity, and wondered why it even matters for you? Join Steph and Chris as they run through Microsoft's transformation from shipping boxed products to always-on online services. Developer Velocity is a critical part of that journey to ensure the teams can keep delivering value to their end users at scale. In this session, you will learn about some of the tips & tricks that Microsoft used along the way.