Hi Mark, you asked about the pre-flight validation in Bicep. It is a feature of ARM, not Bicep per se, and what it does is, it simulates a deployment, so it sends your ARM deployment template (authored directly as JSON ARM or transpiled from Bicep DLS) to the ARM engine and does a series of validations like: 'Does that resource type / Azure service exist in the region I selected?', 'Do I have sufficient quota (CPU cores or similar) for deploying the resources I declared?', 'Are the resource names unique in the given scope?' or 'Will this deployment be stopped by some Azure Policy assignment?', etc. Something that requires context of the 'target environment' that might be difficult to embed as set of input validation rules. Also, preflight and what-if are two separate things.
Hi Mark, you asked about the pre-flight validation in Bicep. It is a feature of ARM, not Bicep per se, and what it does is, it simulates a deployment, so it sends your ARM deployment template (authored directly as JSON ARM or transpiled from Bicep DLS) to the ARM engine and does a series of validations like: 'Does that resource type / Azure service exist in the region I selected?', 'Do I have sufficient quota (CPU cores or similar) for deploying the resources I declared?', 'Are the resource names unique in the given scope?' or 'Will this deployment be stopped by some Azure Policy assignment?', etc. Something that requires context of the 'target environment' that might be difficult to embed as set of input validation rules. Also, preflight and what-if are two separate things.
Hey thanks a lot! Super helpful!!!
Watching this makes me realize that you can always contribute no matter at what level you find yourself in. How can I join this community?
Links to join are in the description! The official community meetings are monthly headed up by the Microsoft Azure Terraform team! Please join us! 🤗
@azure-terraformer I only saw your links there. Will check again. Thanks!