Jonny Eskew

Do you get the same error if you send calls other than `index` to the client?

If sending an unsigned request with `curl` succeeds, are you able to send a request successfully after removing the signing handler altogether? If so, then the error is likely in...

Ah, didn't realize the 500 was coming from your application and not from your elasricsearch service endpoint. Could you take a look at your server logs to find more informations...

> The really vexing cases involve some **commonly-used patterns** for resource naming. Here's an example of a change we could make to `my-module.bicep`. > > ```bicep > // my-module.bicep >...

This idea is half-baked at the moment, but I wonder if there should be a type-level distinction here? Perhaps `resource` would not be a supported output type, but `resourceId` would:...

> I'm not sure from your description why the distinction is valuable to users The distinction is valuable only in the sense that it turns the runtime error reported by...

We discussed this yesterday as a team, and the consensus was that we should block resource-typed module outputs while we explore updating the ARM deployment engine to support nested reference...

While working on a proof-of-concept of the outlining approach proposed above, I encountered a few cases where the ARM code generated would be less than ideal. 1. In ARM JSON...

I believe this would need special syntax to implement in a backwards-compatible way. The `format` function does support passing an array as an argument, but the longstanding behavior of the...

This may require a change to the `IFeatureProvider` interface, as Bicep configuration is discovered based on a template's position in the file system rather than the context in which the...