Hey folks! If you're authoring Plugin Framework b...
# package-authoring
o
Hey folks! If you're authoring Plugin Framework based providers, we have a breaking change in v0.12.0 of the bridge. We're making this break to make it possible to use
ComputeDefaults
and
AutoAliasing
, and we've also made PF based providers use the same
tfbridge.ProviderInfo
as SDKv2 providers. Implementing this, you'll modify your
Provider
constructor (typically in
resources.go
) to return or use the original
tfbridge.ProviderInfo
instead of using a plugin framework (
pf/tfbridge
) version. You'll pass the upstream provider to the
P
field, as with SDKv2 providers, but you'll use
pf.ShimProvider()
instead of
shimv2.NewProvider
. We have examples in our unit tests here: https://github.com/pulumi/pulumi-terraform-bridge/blob/adfd7f99c35316d683a6fcd562f816ac3c765bb2/pf/tests/internal/testprovider/random.go#L64-L66