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.
Turns out that IBM is leading OpenTofu efforts. We might just be done here.
Also Pulumi is technically fucked too. Back to good old shell scripting boys
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.
I don’t know
The bastards can never take away your shell script full of arcane and unreadable curl commands parsed by incomprehensible awk scripts!
IBM is in no way involved in OpenTofu. Afaik they are involved in OpenBao.
Source: I’m the technical lead of the OpenTofu project.
Legend 🫡
Apologies, I got that wrong. Will edit my comment
OpenTofu is under Linux Foundation stewardship, they can find another supporter.
Thanks, I got that wrong. Edited