[Drift] The refresh mistakenly shows a scheduleId change but reports no changes.

[MitchellGerdisch]

I have a program here: https://github.com/MitchellGerdisch/pulumi-work/tree/master/ts-deployment-schedules It sets up deployment settings and a three schedules - including a drift remediation schedule. When drift runs the refresh phase reports that it found 3 scheduleIds to add to state (for the 3 schedules in the program) but also indicates that there are no changes and the update does not run. Note: even if I cause something that does result in the update phase running, no change is applied for the schedule Ids. So, it is mistakenly showing a change that does not exist.

ALSO, if I run refresh locally this false positive does NOT occur even if I have all the same pulumi about settings as used by deployments.

Expected behavior

The false positives should not be shown.

Current behavior

See above.

Steps to reproduce

1. Run this program: https://github.com/MitchellGerdisch/pulumi-work/tree/master/ts-deployment-schedules
2. It will set up deployments and schedules.
3. Modify the drift schedule to run presently.
4. See the refresh phase show the scheduleId changes that are not changes.
5. Run the refresh locally on your workstation and see no such false positives.

Context (Environment)

Affected feature

[komalali]

This is a bug with the display code in the cloud UI. Specifically, the summary display shows a change but the diff display does not.

[komalali]

This might be helped by @pgavlin's work to unify the wasm module with the CLI code

[IaroslavTitov]

Details from internal issue I resolved as duplicate ion favor of this one:

• This is not just an issue with scheduleIDs, but with other properties as well
• This issue so far has only been observed on refresh operation