Shenglong Li

The fix was deployed.

That's odd. I wasn't able to reproduce it in a test CI run: https://github.com/shenglol/test-az-cli-bicep/runs/7436600909?check_suite_focus=true. @pinakighatak is the issue still happening?

What is the OS type of the runner? Also, is the job running inside a container using the Azure CLI image?

Bash actions works because Bicep CLI is installed on GitHub workflow runners. I don't know why the azure/cli action doesn't work since I cannot reproduce the issue, but one workaround...

> Thanks @alex-frankel! > > This time it is failing on the step [Build Bicep In Visual Studio](https://github.com/Azure/bicep/runs/7631374270?check_suite_focus=true#logs) which ran successful on the last try. I'm not sure I understand...

With the current implementation, metadata accepts anything, including resource references, variables or parameters, for example:  However, it probably doesn't make sense to allow metadata to contain runtime values /...

We'll need to update the error message of BCP007 to include metadata declaration: 

Hi, Are you running ArmViz on your local machine? Could you please check if there is any error info in your browser console?

@SvenKempf Thanks for your comments! I'll fix this in our next version :) Best, Shenglong

Yes, I'm talking about [OpenTelemetryLoggerOptions.AddGenevaLogExporter](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/4a23a7e3154ab9990a0624a665e229fef0a294ac/src/OpenTelemetry.Exporter.Geneva/GenevaLoggingExtensions.cs#L31) specifically. Within the extension method `GenevaExporterOptions` is currently created via a constructor, but I think now we can use `OpenTelemetryLoggerOptions.ConfigureProvider` to get it from the...