Marcin Jastrzebski

The replacement PR is https://github.com/Azure/azure-rest-api-specs/pull/20696

@jurjenoskam Are you able to set the parameter explicitly to `null` in the portal as a workaround?

@stephaniezyen Can you triage this with the portal team?

> > Although it does yield a warning: > > The property "value" expected a value of type "string" but the provided value is of type "null | string". >...

If we proceed with excluding the `existing` resource dependency, we should also ensure that it works correctly with symbolic name codegen because we emit `existing` resources to JSON in that...

Yeah, we would need to an additional task to our msbuild targets to enumerate the true dependencies of any particular Bicep module. The logic for that shouldn't be too complicated,...

Agreed. For param files, references to bicep files via the `using` keyword should also be included.

Options to implement this: * We could increase the limit in the runtime. * We could put the content into a variable instead of a JSON expression string literal. (Would...

My expectation would be for the string to be rejected because it's not a symbolic name. However, I think we do need some sort of interop gesture to bridge templates...

@anthony-c-martin During our last discussion, we realized that API version match/mismatch semantics differ on inputs and outputs. I think it'd be worthwhile to explain more about for the community at...