IgnoreChanges unable to ignore set element changes

[t0yv0]

What happened?

Due to #1755 effect of how sets are represented in bridged providers, it is really impossible sometimes to ignore set updates using ignoreChanges.

IN programs like this: pulumi/pulumi-aws#2442 it is not unreasonable for the user to try to workaround incorrect provider diffs by saying this:

    {
        ignoreChanges: ["parameters[*].applyMethod"]
    }

However currently this fails to suppress the diffs in question. To the diff it looks like the elements are added and removed instead of changed in-place. Therefore the diff looks bigger than just applyMethod.

Example

See above

Output of pulumi about

N/A

Additional context

N/A

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).

[t0yv0]

Still don't have a complete picture of how to interpret ignore_changes and implement this is intuitive. Might be worth digging into how TF does it for sets https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle#ignore_changes

In particular I am curious if the set hash is exposed explicitly so you can reference the set hash (or element identity) in your ignoreChanges (currently it's not really user-facing in Pulumi bridged projection), and if not, what is done to correlate numeric indices to set elements and how does ignoreChanges interact with changes that would affect an element's identity.