Continuous diff due to different order of conditions in IntegrationAction resource.

[ringods]

What happened?

Customer reported that Pulumi reports a diff every time because the order of the conditions is not stable:

Example

new IntegrationActionCreateArgs
{
    Name = "p5-create-action",
    Tags = new[]
    {
        "ResourceHealth",
        "Informational",
    },
    ExtraProperties =
    {
        { "Cause", "{{cause}}" },
        { "Current Health Status", "{{currentHealthStatus}}" },
        { "Previous Health Status", "{{previousHealthStatus}}" },
        { "Status", "{{activityLogStatus}}" },
        { "Subscription Id", "{{subscriptionId}}" },
    },
    User = "AzureResourceHealth",
    Alias = "{{resourceId}}-"+name,
    Priority = "P5",
    Source = "{{signalType}}",
    Message = "[Azure Resource Health]: {{resourceId.extract(/([^/]*)$/)}} {{title}}",
    Description = "{{details}}",
    Filters = new[]
    {
        new IntegrationActionCreateFilterArgs
        {
            Type = "match-all-conditions",
            Conditions = new[]
            {
                new IntegrationActionCreateFilterConditionArgs
                {
                    Field = "activityLogStatus",
                    Not = true,
                    Operation = "equals",
                    ExpectedValue = "Resolved",
                },
                new IntegrationActionCreateFilterConditionArgs
                {
                    Field = "level",
                    Operation = "equals",
                    ExpectedValue = "Informational",
                },
            },
        },
    },
    Responders = new[]
    {
        new IntegrationActionCreateResponderArgs
        {
            Id = responder.Id,
            Type = responder.Type,
        },
    },
}

Output of pulumi about

Dependencies:
NAME                                      VERSION
Azure.Security.KeyVault.Secrets           4.5.0
Microsoft.Extensions.DependencyInjection  8.0.0
Pulumi.Opsgenie                           1.3.2
CLI
Version      3.101.1
Go Version   go1.21.5
Go Compiler  gc

Plugins
NAME          VERSION
azure         5.57.0
azure-native  2.20.1
azuread       5.45.0
azuredevops   2.5.0
dotnet        unknown
opsgenie      1.3.2
random        4.14.0
time          0.0.16

Host
OS       Microsoft Windows 11 Pro
Version  10.0.22631 Build 22631
Arch     x86_64

Customer also tried with OpsGenie package v1.3.4 but with the same outcome.

Additional context

https://www.pulumi.com/registry/packages/opsgenie/api-docs/integrationaction/

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[iwahbe]

Thanks for reporting this @ringods. Notes on the issue: It is possible this is an upstream bug. Upstream has opsgenie/terraform-provider-opsgenie#418 which is related in behavior, but on a different resource.

[VenelinMartinov]

Trying to sort out access - looks like our account does not have permissions on this resource so I can not test this. Will update once I sort that out.