Week 14 - Infrastructure as Code

Why use Infrastructure as Code

IaC concepts

Azure Bicep

Bicep in practice

Deploy Bicep from CI/CD

Practice

Assignment

Gotchas & Pitfalls

Glossary: Week 14

Career relevance: Week 14

History of IaC

• Going Further

Slides (PDF)

Going Further

This page is optional. Nothing here is required for Week 14's learning goals or the assignment. Week 14's core is Infrastructure as Code with Azure Bicep: Why use Infrastructure as Code, IaC concepts, Azure Bicep, Bicep in practice, and Deploy Bicep from CI/CD.

Optional deep-dives live in the topic pages below. They are real skills, but they are not needed to pass the week. Skip around.

Topic pages

• IaC tool landscape: Bicep vs ARM vs Terraform vs Pulumi, state files, and how to actually choose
• Layers of IaC: cloud resources vs platform assets vs app config, and why the split changes who reviews your pull request
• Advanced Bicep: loops, conditions, existing references, and Key Vault getSecret
• Deleting infrastructure: incremental vs complete mode, why complete is being deprecated, and deployment stacks
• Checking a template before you deploy: the Bicep linter, bicepconfig.json, and validate vs what-if
• Modules at scale: module registries, versioning, and Azure Verified Modules

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.