<@U02J3T6A8LB> what's the future of crd2pulumi? Is...
# contribute
q
@echoing-dinner-19531 what's the future of crd2pulumi? Is it going to get hoisted into langhost toolchain along with other *2pulumi tools? Asking because we're interested in wider k8s coverage in pulumi-scala and crds are kinda important for operator integration.
e
Going to be looking into that this week! I'm hoping it will turn into a converter plugin like tf2pulumi did.
q
How is language support solved in tf2pulumi now? Can it work with arbitrary language plugins if they expose correct grpc apis?
e
Yup it uses the GenerateProject method on the langauge plugin
q
So crd2pulumi will use the same call in the future, very cool!
e
Probably, will be trying to work out exactly what it needs to do this week. At any rate the plan will be for it to be language agnostic, so other languages can just hook in
l
@quaint-spring-93350 for clarity,
tf2pulumi
is deprecated and replaced by
pulumi convert --from terraform
. I'll be working with @echoing-dinner-19531 on trying to create a
pulumi convert --from crd
so we can also deprecate
crd2pulumi
. No more standalone tools, but this code generated integrated in the core Pulumi CLI.
q
yay, that's great, we're working on supporting
GenerateProject
g
Hey guys, while we are waiting for
pulumi convert --from crd
to be ready, can someone help merging some PRs in
crd2pulumi
, especially the one that fixes support k8s v4 provider. This will really help us until the
crd2pulumi
is officially deprecated.