Marcin Jastrzebski
Marcin Jastrzebski
We don't have any docs that cover this specifically for Bicep. These are just normal system environment variables. Depending on how you're invoking Bicep, the following options may work for...
Yes, we're not picking up the index expression from the parent property which fails an assertion in loop code generation. I'm working on the fix.
It seems like an issue with nested resources under extension resources (unclear if loop involvement affects the bug)
Yeah, I'm not sure there's an agreed upon design for this issue yet. Also, @TarunSunkaraneni picked up the output file location one.
Should we do it more like C# where there's a `#region parameters` and a corresponding `#endregion` declaration below? Otherwise, it's hard to tell if a region is starting or ending...
That's interesting because the problem in C# is that you can't tell which region is ending and the above syntax fixes that.
If regions are mismatched, there should be an error. (The error would be recoverable and would not interfere with authoring of a bicep file anywhere else. It's a good question...
For export as Bicep in the portal, we would need to decompile a single template into a single Bicep file, which should be fairly easy to model in an API....
We discussed this in triage today and the plan is to make changes in the what-if engine to deal with API versions and will restore the original bicep codegen behavior...
I definitely agree that inlining a module into the parent deployment would be challenging. The nested deployment today acts as a nice JSON language scope that makes a lot of...