Learning Infrastructure as Code with Bicep
A student wants to learn how infrastructure can be expressed as code.
Beginner · Student, Developer · Documented building blocks
Scenario overview; the standalone tutorial and its executable artifacts are not yet published. Start with the linked book exercises, which document the existing building blocks.
What Quinzee contributes
A small local deployment makes resource relationships inspectable after each change.
The proposed example
Start with parameters and outputs in a resource-group template, then add explicit dependencies using the infrastructure workshop.
Required capabilities
Bicep compilation and resource-group Incremental ARM deployments.
Boundaries and remaining work
No Complete mode, nested/linked deployments or resource loops. Bicep syntax success is not an Azure compatibility test.
What to verify
- Compile and deploy a minimal supported template.
- Recognize that compiled nested Bicep modules and loops may exceed Quinzee’s supported deployment subset.
Read the three perspectives
- The Book of Quinzee: Deploy your application's resources with Bicep · Primary reference
- The Book of Quinzee: Turn infrastructure into repeatable deployments · Primary reference
- The Book of Quinzee: Provision storage, secrets and configuration · Primary reference
- The Book of Quinzee: Provision event delivery and durable messaging · Primary reference
- The Book of Quinzee: Provision databases and a cache with real engines · Primary reference
- The Book of Quinzee: Deploy application hosts and their identities · Primary reference
- The Book of Quinzee: Deploy monitoring with the application · Primary reference
- Quinzee Administrator’s Guide: Control resources and infrastructure deployments
- Quinzee Internals: Deployments and native engines