<Previous Challenge - Home - Next Challenge>
- You should have completed Challenge 01
Now that you've created your Bicep templates, you would like to create a CI/CD pipeline to deploy these templates to your Azure environment.
- Create a repository and upload your Bicep templates to the main branch.
- Create a CI/CD pipeline using either GitHub Actions or Azure DevOps.
- If using GitHub actions (recommended), a sample workflow (deploy.yml) can be found at
/Challenge-02
of theResources.zip
provided by your coach. - If using Azure Pipelines, it is ideal that you are using an organization that has parallel jobs configured. Otherwise, you will need to request free parallel jobs which will take 2-3 days to complete or set-up paid jobs for a cost.
A sample YAML pipeline (azure-pipelines.yaml) can be found at
/Challenge-02
of theResources.zip
provided by your coach.
- If using GitHub actions (recommended), a sample workflow (deploy.yml) can be found at
- Deploy your environment using the Bicep templates that you created from Challenge 01.
- Verify that you are able to run an automated deployment of your environment using the Bicep templates that you created from Challenge 01.
- Verify that you are able to send a GET or POST request to Echo API (the default API configured in APIM).
- Quickstart for GitHub Actions
- Quickstart: Deploy Bicep files by using GitHub Actions
- Quickstart: Integrate Bicep with Azure Pipelines
- Deploy Azure resources by using Bicep and GitHub Actions
- Deploy Azure resources by using Bicep and Azure Pipelines
- In your GitHub Actions workflow or Azure DevOps pipeline, rather than having a single task that deploys your Bicep template straight to Azure, extend it to include some or all of the suggested tasks:
- Linting and validating your Bicep code.
- Adding a preview job to see what will be deployed to Azure and an approval step before deploying your template.
- Adding a test job to verify that your template deployed correctly.