Absolutely appalled to see the pulumi component provider has been deprecated with zero docs on how to migrate to the new mechanism. I’m essentially now in a position where my component can’t be maintained or upgraded. https://github.com/pulumi/pulumi-component-provider-go-boilerplate Is there any thought given here to how these decisions affect the ability to maintain community resources? This is supposed to get easier over time, not harder. Genuinely considering migrating all of my customers over to Terraform so I don’t have to constantly hit a moving target

Hey Lee, my understanding is this was more of a "you shouldn't use this for new things" as opposed to "everything should stop using it". If your current components are working for you then you can just keep them like that for now, the framework the boilerplate depended on isn't going away. The new go-provider is supposed to be a much better experience, I'll flag it up to the providers team that a migration doc would be good to have even if the old boilerplate code is going to keep working.

Running production infrastructure on a framework that’s deprecated and isn’t going to get any further updates isn’t really tenable. If there’s a new way of doing things, there should be a migration path.

the framework the boilerplate depended on isn’t going away

No, it’s just archived and deprecated, which means eventually I’ll need to migrate things

Hey Lee, the deprecation of https://github.com/pulumi/pulumi-component-provider-go-boilerplate was on my team. I apologize for the lack communication around it. Just to clarify, while the boilerplate repo was archived, all the SDKs it used (github.com/pulumi/pulumi/pkg/v3, github.com/pulumi/pulumi/sdk/v3) are still supported. Providers built against those libraries do not need to migrate unless you want to do so to take advantage of some of the conveniences in the new pulumi-go-provider library.