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

this is likely a bug, can you show me what errors your see?

could you file an issue in the azure-native repo with code repro

here? ok, I will
<https://github.com/pulumi/pulumi-azure-native/issues>

in the meantime, you can work around this using this <https://www.pulumi.com/docs/intro/concepts/resources/options/replaceonchanges/>

<https://github.com/pulumi/pulumi-azure-native/issues/2253>

<@UCWG26BH7> replaceOnChange seems to help pulumi do the right thing, but still fails to complete the replacement :stuck_out_tongue:

Diagnostics:
  azure-native:documentdb/v20220815:SqlResourceSqlRoleAssignment (management-cosmos-rw-rbac-assignment):

    error: cannot create already existing resource '/subscriptions/ad7f52f6-6c6a-4e2a-bb4e-a4b61353d213/resourceGroups/mk-beacon-platform/providers/Microsoft.DocumentDB/databaseAccounts/management-store-accounta5c440a0/sqlRoleAssignments/245cd1b9-ffb4-7eb7-5f22-865e9947c705'

add this as well
<https://www.pulumi.com/docs/intro/concepts/resources/options/deletebeforereplace/>

ok, so this actually has done the job, and even though it feels like it should have been handled by the provider, as it's always the same for this type of entity, it's not a bad workaround

on the other hand we've figured out that some changes to dapr components aren't even picked up by pulumi, and resource is 'unchanged', so I'll report it as another issue

&gt; feels like it should have been handled by the provider
we’ll triage that bug