Testing Bicep Deployments
A DevOps engineer maintains Bicep templates describing an application's infrastructure.
Intermediate · DevOps engineer · 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
Local ARM resources let you observe supported dependency and update behavior before provisioning remote resources.
The proposed example
Deploy the infrastructure workshop’s resource group, inspect outputs and operations, change a parameter and redeploy incrementally.
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 the template and inspect the emitted ARM resource types.
- Compare deployment outputs and inventory before and after the change.
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