This message was deleted.

What's the configuration change that you are making? It's possible that that change does not support an in-ppace update. Also you should consider setting the resource option

protect

so that you don't accidentally execute a replacement that would delete the original db resource.

Basically adding a managed identity … added:

Identity = new Pulumi.AzureNative.Sql.Inputs.ResourceIdentityArgs
            {
                Type = Pulumi.AzureNative.Sql.IdentityType.SystemAssigned
            },

Hmm that's interesting...can you run a preview with the

--diff

flag and post the detailed diff for your db resource here?

Sorry for delay … here is an example:

--azure-native:sql:Server: (delete-replaced)
 +-azure-native:sql:Server: (replace)
      ~ administrators: {
          ~ login: "sp-pulumi-production" => "sp-pulumi-nonproduction"
        }
 ++azure-native:sql:Server: (create-replacement)
      ~ administrators: {
          ~ login: "sp-pulumi-production" => "sp-pulumi-nonproduction"
        }

Your detailed diff seems to indicate that there was already an identity assigned. It's possible that changing the identity is not an in-place update. Also the

administrators

property and the

identity

seem to have the same description. Even though you set the

identity

property it seems that the

administrators

property is changing? That seems odd. Any chance you can post the entire code related to the SQL Server resource?

i think the problem is the one listed here : https://github.com/pulumi/pulumi-azure-native/issues/1738 … basically Azure API not Pulumi is causing this ridiculousness 😅

Ah yes. Yeah the real issue is described in this comment: https://github.com/pulumi/pulumi-azure-native/issues/1738#issuecomment-1144987215.