terraform-provider-carvel VS terrajet

terraform-provider-carvel

And to my personal opinion they would've better spent some resources to contribute to the target providers instead of embedding or directly code-generating (https://github.com/crossplane/terrajet) from Terraform. Spreading the efforts and resources doesn't really help that much with the existing Terraform issues.

So, I find both pulumi and crossplane rather parasitic for the existing Terraform Provider Infrastructure. Actually fixing the bicycle would've been better than strapping a jet engine on top.

For me, this situation is very similar to the long resolved issue with docker multistage... with myriads of CLI tools on top obsoleting in result.

We have implemented Terrajet (https://github.com/crossplane/terrajet) that generates CRDs that's completely compliant with Kubernetes Resource Model; references, label selectors, spec/status, no TF state blob saved anywhere.

Check it out!

Crossplane comes to my mind when thinking of using the GitOps way to provision infrastructures. Unfortunately, I think there isn't a Vault Crossplane provider at the moment but there's a terrajet project that allows you to generate Crossplane providers from Terraform providers. Might be a long shot and seems overly complex for a use-case like yours, but worthwhile if you plan to let ArgoCD manage everything.