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

Hey, is there an ETA for dynamic resource providers to be supported in golang?
<https://www.pulumi.com/docs/iac/concepts/providers/dynamic-providers/>

There's no plan to ever do dynamic providers for Go, but we have plans for a slightly different technology we've been calling inline providers and we'd support that in Go.

From a user POV there very similar ideas, but inline providers just relies on running your program so it piggy backs on the --run-program support we added for refresh/destroy.

Gotcha, asking because I'm learning today that newrelic doesn't have support for like 90% of their IAM stuff in terraform (and therefore pulumi) and having the ability to extend the provider to have pulumi handle state management would be a godsend

Also to handle the DAG creation and timing of resource management etc.

Really this is less of a pulumi issue and more of a new relic issue

yeh that makes sense, sort of thing we'd want to support. I'd watch the dynamic provider ticket, if we do inline providers we'll post to that issue.

Mind tossing me that ticket so I can mash f5 on it for the coming weeks lol?

<https://github.com/pulumi/pulumi/issues/3825>

Since you're already writing in Go, you might want to look at Pulumi Go Provider framework and you can write your own resources: <https://www.pulumi.com/docs/iac/guides/building-extending/providers/sdks/pulumi-go-provider-sdk/>

<@U02FZC2RE0Y> - I was thinking about this, and it's kinda where we ended up. I was hoping to extend an existing provider.

Could you maybe take the Pulumi provider as a Go dependency?

Me either. I don't think it would gain you much on second thought.

lol no worries. We have a solution now that's gonna work until new relic gets their shit together and decides after 4 years to include basic IAM functionality in IAC