-
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
ProviderMeta Issue enrolling GCP resource into PlanResourceChange #1822
Comments
The issue happens here: pulumi-terraform-bridge/pkg/tfshim/sdk-v2/provider2.go Lines 280 to 295 in f6013b6
Looks like we try to coerce the GCP transport.Config value into a cty.Value and fail. The GCP config is defined here: https://github.com/hashicorp/terraform-provider-google-beta/blob/99afea8acf81d576b882ec7b4418979139a00e1a/google-beta/transport/config.go#L161 I believe this bit is likely untested since AWS does not define a providerMeta at all. |
PlanResourceChange does not seem to help with pulumi/pulumi-gcp#1874 as detailed in pulumi/pulumi-gcp#1874 (comment) so I am going to let it be for now. EDIT: Discovered this was false. PlanResourceChange change indeed fixes pulumi/pulumi-gcp#1874, so I'm picking this back up. |
fixes #1822 and unlocks pulumi/pulumi-gcp#1874 `ProviderMeta` seems to be an old experimental feature of TF which has not picked up. AWS does not use it and GCP uses it only for one thing - setting UserAgent strings: modular-magician/terraform-provider-google-beta@6cf6c51 The meta we receive does not match the schema provided and does not contain the module_name property. We should set it to null and potentially revisit if this causes issues. I've tested it for the GCP resource in #1825 and works fine. I've opened #1827 as a follow-up to test with one of the resources which actually use the ProviderMeta. --------- Co-authored-by: Ian Wahbe <[email protected]>
What happened?
While working on pulumi/pulumi-gcp#1874 I attempted to enroll the resource into PlanResourceChange in order to address the diff issue.
Diffing fails with the following error:
Example
Running
TestConnProfileUpgradePermaDiff
in pulumi/pulumi-gcp#1890Output of
pulumi about
bridge commit 282c9dd
gcp commit 768e01e
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).
The text was updated successfully, but these errors were encountered: