The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*
Built with ❤️ by the HackYourFuture community · Thank you, contributors
Found a mistake or have a suggestion? Let us know in the feedback form.
Why use Infrastructure as Code
hyf_week_14_edited-subtitled.mp4
Welcome to Week 14! Every Azure resource you have used so far, the shared Postgres database, the storage account, the Container Apps job, was provisioned for you. In Week 6 you even ran az group list and found you were blocked from creating a resource group yourself. This week you learn how teams create that infrastructure properly: not by clicking through the portal, but by writing it as code.
Infrastructure as Code (IaC) means defining your cloud resources in version-controlled files that you deploy the same way every time. On Azure, the native tool for this is Bicep.
By the end of this week, you will author Bicep templates, deploy them with the Azure CLI, refactor them into reusable modules, preview and apply them from GitHub Actions, and tear them down cleanly: the reproducible-infrastructure skill the final-project capstone needs.
az deployment group create and verify it in the portalwhat-if on a pull request and create on merge via GitHub Actions (the Week 5 bridge for infrastructure)Optional out-of-week reading: Bonus - AI-assisted data enrichment