Crossplane has also had internal providers in development for 3 years. Bottom line is unless the actual cloud provider is devoting developer resources to a provider(like they do for the TF providers), it’s unlikely to happen.
I guess I need to start looking deeper into this, and the potential for importing existing infrastructures into pulumi’s purview. But I’m hesitant - I don’t want pulumi to pull a Hashicorp. I’m wondering if it’s best to just go with CFN and Bicep.
Isn’t Pulumi moving to native API stuff instead of the tf provider?
They wish. Nobody is gonna replicate that effort successfully any time soon.
You’d sooner get the cloud providers to standardize on an api.
I mean, they have AWS Native (in preview) and Azure Native. So it’s a little more substantial than a wish.
Crossplane has also had internal providers in development for 3 years. Bottom line is unless the actual cloud provider is devoting developer resources to a provider(like they do for the TF providers), it’s unlikely to happen.
I guess I need to start looking deeper into this, and the potential for importing existing infrastructures into pulumi’s purview. But I’m hesitant - I don’t want pulumi to pull a Hashicorp. I’m wondering if it’s best to just go with CFN and Bicep.
If you’re migrating from tf, OpenTofu might be a better option. I mostly like Pulimi for the language options.
I don’t know