TestRegress170 fails under latest bridge changes

[VenelinMartinov]

Describe what happened

https://github.com/pulumi/pulumi-hcloud/actions/runs/9451894942/job/26034396438?pr=525

Seems to expect no diff but gets a diff.

Looks like a regression on #170

Sample program

.

Log output

  "response": {
    "stables": "*",
    "changes": "DIFF_SOME",
    "hasDetailedDiff": true,
    "diffs": ["networks"],
    "detailedDiff": {
      "networks[0].networkId": {
          "kind": "UPDATE"
    }
  }
  },

Affected Resource(s)

No response

Output of pulumi about

.

Additional context

No response

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

[VenelinMartinov]

Reproes with bridge master

[iwahbe]

P1 because it's blocking the next bridge release.

[iwahbe]

I have confirmed that the regression is genuine (and not overfitting from the test).

[iwahbe]

A binary search has shown that "ba48631b Enable DiffStrategy PlanState by default (#1976)" is the last good commit on the bridge, "b012fa8e Fix proposed new unknown blocks (#2060)" introduced the regression.

[iwahbe]

This looks like a bug in upstream: hetznercloud/terraform-provider-hcloud#650. I have confirmed that Pulumi can use the same workaround as TF suggests. I'll bake the work-around into a transform so we don't expose the change to our users. I believe that we are safe to release the bridge.

[pulumi-bot]

Cannot close issue:

• does not have required labels: resolution/

Please fix these problems and try again.