You will work in a separate for of this repository in GitHub because in a later challenge you will trigger GitHub actions when code is merged to main and you don't have contributor permissions to this repository.
All Azure resources will be provisioned in one Resource Group that you create.
The following image illustrates the steps in this challenge
- Determine and configure your development environment, shell and toolset to use. Some options are
- GitHub Codespaces
- Docker Desktop
- Directly on local machines
- PowerShell or Bash (or other shell of choice like ZSH, fish, )
- Azure PowerShell or AZ CLI (locally, in container or Azure Cloudshell)
- Linux, Mac or Windows with Subsystem for Linux
- Fork the repository and make a clone
- Log in to Azure and create a resource group
- Create a fork of this repository
- Clone the repository in a development environment
- Install the hey load testing tool (not required for codespaces or devcontainer)
- Install Azure CLI extension for Container Apps (not required for codespaces or devcontainer)
- Log in to Azure
- Create a resource group with the naming convention "[seven letters]-rg" in an Azure region of choice
- Repository forked to your GitHub account
- Repository cloned
- A resource group created
- Azure PowerShell Documentation (learn.microsoft.com)
- Azure Command-Line Interface (CLI) documentation (learn.microsoft.com)
- Fork a repo (github.com)
- hey (github.com)
- az containerapp (learn.microsoft.com)
- New-AzResourceGroup (learn.microsoft.com)
- az group create (learn.microsoft.com)
- Install Bicep tools (learn.microsoft.com)
- View the solution here: Challenge 1 - Solution
- Challenge 1: Setup the environment
- Challenge 2: Deploy Container Apps Environment and troubleshoot Container Apps
- Challenge 3: Split traffic for controlled rollout
- Challenge 4: Scale Container Apps
- Challenge 5: Configure CI/CD for Container Apps
- Challenge 6: Protect Container App with API Management
- Challenge 7: Enable Container App authentication