This message was deleted.

@fierce-xylophone-92490 it’s almost certainly easier to bridge the bitbucket provider

The terraform one, you mean?

you actually don’t need to know a whole lot of go except module management, but that’s valid. I’ll see if I can try bridge one tomorrow

If you can make your work public I’d love to read through it.

there are a bunch here: https://github.com/lbrlabs/

Thanks! Do they have downsides besides not being language agnostic?

Do they have downsides besides not being language agnostic?

That's the big one, it limits your provider to only being used by python users, while a non-dynamic provider can generate SDKs for every language. They're also relying on closure serialisation to work, which when it works is awesome but is a nightmare to debug when it doesn't work (this isn't unique to Pulumi, we're just using cloudpickle internally). They're also highly coupled to the SDK version which makes it very hard for us to update them. We've been looking at doing new dynamic providers that would be a separate library with their own update cadence but it's not been deemed a high enough priority to commit to yet.