Mikhail Shilkov

Moved to `pulumi-kubernetes` as the k8s provider has its own diff calculation implementation

Hey @CraftyFella thanks for your request. Doesn't `connectionStrings` output property work for you? https://www.pulumi.com/docs/reference/pkg/azure/cosmosdb/account/#connectionstrings_nodejs

We derive this API from the Terraform provider, so any change like this would likely need to be contributed upstream

@stack72 If I recall correctly, custom timeouts aren't supported in the Azure provider

I've heard about this issue before, but it's weird we don't hit it in our CI. Anyway, we may need to consider adding retries to [here](https://github.com/pulumi/pulumi-azure/blob/master/sdk/nodejs/appservice/zMixins.ts#L838) similar to [this](https://github.com/pulumi/pulumi-azure/blob/master/sdk/nodejs/eventgrid/zMixins.ts#L147).

Thanks for highlighting this problem! As I mentioned above, the retry workaround should be fairly simple. I would love to see a community PR from one of you folks, otherwise,...

Another similar error that we are getting today is that the keys are retrieved successfully but they don't contain the `eventgrid_extension` one. Sounds like https://github.com/Azure/azure-functions-eventgrid-extension/issues/73. Looks like a good nudge...

This sounds like an upstream issue tracked in https://github.com/terraform-providers/terraform-provider-azurerm/issues/10602 (and described in https://github.com/terraform-providers/terraform-provider-azurerm/issues/10442)

While the upstream issue is open for half-a-year, what's the workaround to apply in Pulumi programs? Today, I got the failure while creating an instance of Azure API Management. The...

Does the error come from the `VirtualMachine` resource, or rather from the `NetworkInterface`? The issue sounds somewhat similar to #365, although the error is different. My guess is that you...