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

Actually I wonder if all I need is a <https://www.pulumi.com/docs/intro/concepts/resources/#authoring-a-new-component-resource|custom component resource>

The component resource approach seems to have some downsides - namely I seem to only be able to manage creating a resource and not the update/delete cycles like you can with a dynamic provider

<@U01QN11FSRF> What solution did you end up going with for this?

<@U01RZU8JETG> I wasn't able to use Go for this without a lot of extra effort to build out a custom provider, so I implemented the dynamic provider in JS. I didn't have a lot of time to invest in this piece of the project unfortunately. Here's the dynamic provider in JS if you're interested: <https://github.com/cwinters8/pulumi-aws-godaddy-dns/blob/main/providers/godaddy.js>

The alternative is to build out the same functionality using this boilerplate: <https://github.com/pulumi/pulumi-provider-boilerplate>

Ah yep too bad it couldn't be done (quickly) in Go, but your solution doesn't look bad at all! We're looking to encapsulate some custom tooling with a custom provider, so it's good to see some real examples

Yeah it was fairly simple to do in JS. I really like the concept of the dynamic providers, just wish they were supported in Go projects. The big downside of the implementation is that now I have two different stacks I have to spin up. But that's a tradeoff I was willing to make for the time savings