No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Having problems to provision new CosmosDB Instances, seems like the problem is happening on the azure go sdk/azure api. Terraform AzureRM created a PR with a workaround on this problem: <https://github.com/terraform-providers/terraform-provider-azurerm/pull/7189>

Any idea when it'll be reflected on Pulumi after it's merged? (Not demanding or something like that, just curious about how is the process when there are changes in the Terraform Providers. :slightly_smiling_face:)

<@UTF6UGW4B> this is related to the problem that you posted yesterday.

yes it is, thanks for pinging me. :slightly_smiling_face: yesterday i reported a bug for azure. So hopefully there will be no need for any kind of workaround soon.

We usually update our provider within two days after TF releases a new version