This message was deleted.
# package-authoring
s
This message was deleted.
a
Hi @worried-energy-90920. If you got this working, great. 😄 Please ignore the rest of the message. The bridge has two muxing mechanisms, one too combine a TF provider and a Pulumi Provider. That is
MuxWith
, what @big-architect-71258 mentioned. There is also a mechanism specifically for mixing a plugin framework based provider with a sdk based provider. As an example, pulumi-akamai uses it: https://github.com/pulumi/pulumi-akamai/blob/0c0f10f065c293bf92d8ae514951779f29ca359a/provider/resources.go#L75-L89 To upgrade your provider, there are instructions here: ## How to Upgrade a Bridged Provider to Plugin Framework.
w
hi, thanks for your input! 👍 that was super helpful as i actually tried to get it working with
pf.MuxShimWithPF
but missed the context parameter... (sometimes it's like you are running against a wall and don't see the stupidly easy way... 😅) now i need to find a way to use the automapper and still keep my old resource namespaces but thomas provided some ideas on that already.