Microsoft Reactor

We've explored how we can deploy a container to Azure Container Instances or Azure Kubernetes Service, now let's automate that process!
A CI/CD pipeline (Continuous Integration/Continuous Deployment) enables your application to be automatically tested and deployed when changes are made to the code.
We'll be exploring how to apply this with GitHub Actions.
GitHub Actions allow you to configure specific actions that trigger when events occur in your GitHub repository.
In our case we'll be reacting to changes made to our main branch and triggering an action that builds our code, constructs a container, uploads it to our container registry and deploys that container into Azure.
This means that the live version of our application should also reflect the current main version of our code preventing our deployed code from drifting from the currently committed state.

Speaker: Sam Wronski, Regional Cloud Advocate, Microsoft
Sam Wronski is a Regional Cloud Advocate at Microsoft focused on empowering the San Francisco area to build awesome things with Azure. Sam has spent years building applications and tooling powered by containers.
He's run the World of Zero channel on YouTube for the past 5 years where he's taught software engineering and game development.