-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disentangle deciding DiffResponse from detailedDiff #2293
Labels
Milestone
Comments
This was referenced Aug 9, 2024
I've hit #1501 in pulumi-azure while rolling out PRC: pulumi/pulumi-azure#2322 (comment) One of the tests produces a diff due to pulumi-terraform-bridge/pkg/tfbridge/provider.go Line 1122 in 46d7e98
The diff has no details and no explanation and should not be there as the stack has had no changes. |
6 tasks
This was referenced Aug 30, 2024
VenelinMartinov
added a commit
that referenced
this issue
Sep 17, 2024
This exposes the detailed diff in the cross-test interface for both TF and Pulumi allowing us to write tests which assert on that. Also adds a cross-test for #1696 for the existing `TestChangingMaxItems1FilterProperty`. This is one of the cases where the detailed diff is load-bearing for the diff decision. The cross test verifies that TF also finds a diff here, so our core diff algorithm must be making the wrong decision. Related to #2293
VenelinMartinov
added a commit
that referenced
this issue
Sep 20, 2024
Adds a `DiffEqualDecisionOverride` to the shim layer which allows provider implementations to specify a diff decision instead of relying on the shim layer to do that. Also adds a `DiffEqualDecisionOverride` to the PRC sdkv2 implementation which opentofu does. Also adds a feature flag `EnableAccurateBridgePreview` which guards this feature. will fix once rolled out: #2293 will fix once rolled out: #1501 will undo once rolled out: #1502 as the underlying issue was fixed during the PRC work. Stacked on #2380
fixed in #2379 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
This interaction between detailedDiff and DiffResponse needs to be removed:
pulumi-terraform-bridge/pkg/tfbridge/provider.go
Line 1122 in 46d7e98
Resolves: #1501
This will undo: #1502
Assumes PlanResourceChange is enabled for roll-out. This change should be flagged together with the other changes for the accurate preview work.
Undoing the change risks regressing two important customer-visible behaviors, epic will have tasks to follow up so we have solutions for these:
Out of scope:
markWronglyTypedMaxItemsOneStateDiff continues to edit diff results for now; this is out of scope as it does not
interact with detailedDiff AssertionError in
lambda.EventSourceMapping
for version 6.13 pulumi-aws#3092similarly this code may remain:
pulumi-terraform-bridge/pkg/tfbridge/provider.go
Line 1177 in 46d7e98
The text was updated successfully, but these errors were encountered: