Examples of module implementation are done in JSON both with parameter usage sections in readme.md
files and in different parameter files used for validation deployments.
This makes sense if you are a module developer, however in a "customer first" point of view, CARML is consumed to build solutions with multiple modules. As a solution developer expect I shouldn’t have to do “extra” work with changing quotes form the JSON Example to Bicep that only supports single quotes ‘’.
- Update readme.md parameter usage to show bicep syntax
A separate issue and task is created to explore the feasibility of having bicep based validation deployments.
Examples of module implementation are done in JSON both with parameter usage sections in
readme.mdfiles and in different parameter files used for validation deployments.
This makes sense if you are a module developer, however in a "customer first" point of view, CARML is consumed to build solutions with multiple modules. As a solution developer expect I shouldn’t have to do “extra” work with changing quotes form the JSON Example to Bicep that only supports single quotes ‘’.
A separate issue and task is created to explore the feasibility of having bicep based validation deployments.