Coming into Pulumi, my understanding was that, if Pulumi does not have a provider for something (in my example case managing a self-hosted mongodb), we could use any given terraform provider for that thing within pulumi. But the documentation is pretty scarce on it, and I am starting to believe, and I assume that's just what it is, that with that terraform bridge you are able to CREATE a provider for Pulumi FROM a terraform provider, but basically providing one ready made pulumi provider utilizing any given terraform provider. So is this correct? Tl;dr: Is my assumption correct that pulumi can NOT utilize terraform providers as fallback intrinsically, just provides a way for you to provide a pulumi provider utilizing a terraform provider with the terraform bridge?

@cuddly-easter-41456 we have the concept of Terraform-bridged providers. It is still a manual setup to build out a Pulumi provider based on such a TF provider. Take the Github provider as an example. The Github repo behind it is a Pulumi provider, but we implement how TF resources are exposed as Pulumi resources: https://github.com/pulumi/pulumi-github/blob/master/provider/resources.go Together with it comes the whole build setup to generate & publish the different language SDKs. You have a starter video on PulumiTV describing the process:

Great thank you, will take a deeper look into this