GitHub Actions

Back in November, GitHub announced its OpenID Connect capability for cloud deployments was generally available. This has been on my list to try out, and I finally managed to get around to it! With scenarios like this, I prefer to do something real and hands-on, rather than mocked, or a proof of concept. I decided to refactor my GitHub Action workflows for cloudwithchris.com, removing the need for secrets stored in GitHub. In this post, I outline my journey through this.

I recently wrote a blog post about using GitHub Actions to automatically add a GitHub Issue to a GitHub project (Beta) when the issue is opened. I received a question from my colleague and maintainer of the promitor and KEDA Open Source (OSS) Projects, Tom Kerkhove on doing the same with a user-owned GitHub repository, rather than organisation-owned.

I’ve been following the GitHub Projects beta for a while now, and have been fortunate to be accepted as an early adopter. I’m a big fan of the direction, and the flexibility. One of the limitations I’ve noticed is that there’s currently no built-in way to automatically add an issue to a project board. It’s on the backlog, but not yet available. Fortunately, GitHub Actions has us sorted. I’ll walk you through a sample I put together to do exactly that.

Did you know that Static Sites can help you build performant sites that easily scale globally? Better yet, they can be incredibly cost-effective!

Chris is a Cloud Solution Architect at Microsoft. He’ll provide an overview of GitHub and explore how GitHub Actions can be used to build and deploy your own static sites (or other apps!) to Azure.

I recently started thinking about the typical setup process for a GitHub Action Workflow which will deploy into Azure. Typically, the process is to use the Azure/login GitHub Action, and then use the azure/cli or another Azure GitHub Action to deploy into GitHub. This is a nice approach. However, from my initial research - I wasn’t able to see a way use the Azure/login GitHub Action to deploy into Azure using a System Assigned Managed Identity. This got me wondering, is this possible?

We often hear about Kubernetes, App Services, VMs and more. What about static sites? The Static Content Hosting pattern can be cost-effective, and when combined with a CDN can be incredibly performant! We will get hands-on, showing how these resources come together into a Cloud Architecture.

In this session, Chris is joined by Karl Cooke - Implementation Specialist at Action Point Technology Group, Blogger at https://irishtechie.com. Chris and Karl talk all about the CloudWithChris.com architecture and the decisions surrounding the GitHub setup that drive the deployment and management of CloudWithChris.com.

Microsoft Cloud Advocate Dean Bryen is joined by guests Carole Logan (developer and tech lead based in Glasgow) and Chris Reddington (Microsoft Cloud Solution Architect) as they take you through the end-to-end process of editing, committing and deploying code across different platforms and tools. We’ll end with a Q&A session and next steps for you to try the process out for yourself to see how agile and collaborative it is. We look forward to seeing you there!

Chris is a Cloud Solution Architect at Microsoft. He’ll provide an overview of GitHub and explore how GitHub Actions can be used to build and deploy your own static sites (or other apps!) to Azure.