Alex Frankel

I assume it is ok if two issues have the exact same title? Would be cool if we can have automation that identifies and auto-closes duplicates.

Great feedback -- thanks @onionhammer. @ucheNkadiCode can we take a look at this one and turn it into individual issues?

@ucheNkadiCode should we close this in favor of the other issues you created, or do you want to leave this open?

Here's a repro file that will show the esc issue: ```bicep param foo string param bar string param baz string output foo string = foo output bar string = bar...

This is a known issue with the ARM Template Runtime, not Bicep in particular. We are working on a fix on the service side. We will update this issue accordingly...

The goal is to fix the runtime so you won't need this workaround in either bicep or ARM. We have the work scheduled to fix this in the next 2-3...

No update unfortunately. I know @majastrz is very close to picking this up, but I don't believe the work has started yet.

You would need to use a ternary expression on each property to only access the `loadBalancerConfig` properties if `loadBalancer` is true. Something like (I haven't tested this e2e): ```bicep param...

Thanks for reporting @dgard1981 - this is a similar case to `/locks` above. They are both extension resources, which means they can be appended to any currently existing resource (that...

*Originally reported with Azure/bicep#791* -- **Bicep version** Bicep CLI version 0.1.223-alpha (895cac24a7) **Describe the bug** When defining a vnet resource, the *properties* attribute isn't being marked as required. Per ARM...