No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

this is awesome! could you DM me your email, would love to send some pulumi swag as a thank you!

<@U03MA0PB3DE> how does the workflow differ for the plugin-framework type of tf providers? Have you successfully Pulumi-ized one of those?

<@U03MA0PB3DE>
Maybe this is a bit bold :smirk:, but I created a Cookiecutter template for wrapping a TF provider into a Pulumi provider using TF bridge. And I can say from a couple of people here (I think <@U01G51145NH> is one of them) that they were happy using it, because especially for a TF provider which hides the provider entry point in the internal path it automatically creates the required `shim` module or for a TF provider which has an invalid `go.mod` it is able to figure out the correct module reference.

<https://github.com/tmeckel/pulumi-tf-provider-cookiecutter>

<@UCWG26BH7> had a short discussion with <@UFPFMDBTK> about it. He wasn't that enthusiastic as you, because it's Python and not Go. It's quite an alien in the Pulumi ecosystem. My intend was to make this boilerplate repository superfluous.

<@U03MA0PB3DE> One important point about the template I forgot to mention: it supports wrapping Tf providers using the TF SDK v1,v2 and the new TF Plugin-Framework by simply selecting the version of the SDK. The template does the heavy lifting, which TF Bridge version (GO module) has to be used and what code has to be used behind the scenes.

&gt; how does the workflow differ for the plugin-framework type of tf providers? Have you successfully Pulumi-ized one of those?
Hey <@U01G51145NH> we did it for the Spotify provider. We’re also working with one of our customers (who we generate a TF provider from OpenAPI) to convert to Pulumi

yes, the spotify one is sdkv2: <https://github.com/conradludgate/terraform-provider-spotify/blob/d5b48fa28e4c531e41d771a2fa1b23a97da21b92/spotify/provider.go#L4>

your blog claimed your approach will work with plugin framework tf providers too, that's why I'm double-checking (haven't been able to replicate that on my own yet)

aah sorry good point, yes it does work although we haven’t launched one in prod that way so the verification is certainly less rigorous

will definitely re-read your blog post if you update it with those lessons learned :wink:, thanks!

please do ! :smile: Fun time in IAC right now, a little spicy, but mostly fun !

hosting a happy hour in SF during Hashiconf if anyone who’s in the area wants to come talk about this ! <https://lu.ma/event/manage/evt-2p3lGpfUTBUaETS/guests>