-
Notifications
You must be signed in to change notification settings - Fork 0
Home
forsback edited this page Dec 31, 2022
·
28 revisions
Bicep deployments are typically done using one parameter file that maps directly to the Bicep file. Each parameter file needs to have exact parameter match for the deployment to succeed. This leads to a situation where parameter definitions are hard to share for other deployments. It is also beneficial to make Bicep deployments modular. We will further show that using YAML for variable handling is beneficial and easier to maintain, as it is more human readable than the JSON format. We will be using MS provided resource Bicep modules in the example (https://github.com/Azure/ResourceModules). These contains extensive and well defined Bicep templates with related documenation.
- Bicep resource modules, https://github.com/Azure/ResourceModules