[TFPF] Upstream provider is now a mixed SDK/TFPF provider #1051
Labels
area/providers
awaiting-upstream
The issue cannot be resolved without action in another repository (may be owned by Pulumi).
blocked
The issue cannot be resolved without 3rd party action.
impact/usability
Something that impacts users' ability to use the product easily and intuitively
kind/bug
Some behavior is incorrect or out of spec
resolution/fixed
This issue was fixed
What happened?
As of the most recent release, the
google-beta
provider has begun to include TFPF resources alongside existing TF SDK resources. To support bridging these resources out of the box, we will require the tfbridge muxer work to be applied to this provider as well.Expected Behavior
Resources like this: https://github.com/pulumi/terraform-provider-google-beta/blob/patched-v4.60.0/google-beta/data_source_dns_keys.go
Should be bridged into the Pulumi provider as expected, rather than backported as a
reverted
resource: https://github.com/pulumi/terraform-provider-google-beta/blob/patched-v4.60.0/google-beta/data_source_dns_keys_reverted.goSteps to reproduce
Run
make tfgen
on a new tag of the upstream provider. Notice that new TFPF resources are missing from the output.Output of
pulumi about
N/A
Additional context
Existing epic tracking TFPF work in the bridge as well as the Muxer work mentioned above:
pulumi/pulumi-terraform-bridge#744
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: