Consider porting Terraform Provider to a Crossplane provider

[danielloader]

What is currently missing?

Currently evaluating Crossplane for in-kubernetes cluster automation, I currently use the Aiven Operator model directly but if I have Crossplane in use it makes sense for a common abstraction in platform engineering to adopt.

How could this be improved?

Maintaining a port of this provider via https://github.com/crossplane/upjet project and publish the resulting provider to the Crossplane/Upbound marketplace.

[Serpentiel]

Hey, @danielloader! 👋

Have you checked https://github.com/pulumi/pulumi-aiven out?

Also, could you please elaborate if there are any downsides on using the Pulumi Terraform bridge instead of creating an actual Crossplane provider by our team?

I did a quick search but I wasn't able to find any way to convert Pulumi provider into a Crossplane provider. Some more information on that would be very appreciated.

[danielloader]

Thanks for the reply, I pasted in the wrong links in the original post, I've updated them to point to Upjet instead.

Yeah I've been doing an evaluation of Crossplane vs tf-controller vs Pulumi, and Aiven was the only provider in my POC that was missing in the Crossplane prototype.

This isn't an urgent request just figured I'd launch an issue to gather interest and ask about feasibility. On paper using Upjet to create a provider is relatively straight forward.