I like to have support for openapi 3.0 and 3.1

[thinkrapido]

I like to have support for openapi 3.0 and 3.1

[Peefy]

/assign @amyXia1994

[amyXia1994]

Welcome @thinkrapido ! 👋 👋

In order not to block your adoption, a temporary solution could be first to convert your openapi 3.0+ spec to openapi 2.0, and then use the kcl-openapi tool to resolve it to KCL. The LucyBot api-spec-converter (online version, GitHub repo, Node.js module) can be used to do that convertion.

The initial scenario that requires conversion between openapi & KCL is based on the k8s resources, and openapi 2.0 support is enough for that. Now that KCL is aimed to be generally used for common configuration and policy scenarios, the full support of openapi is indeed necessary. I'll solve that later and welcome to contribute!
Since you mentioned, could you share more information about your openapi spec and possible usage of KCL? 😃

[amyXia1994]

The go-openapi lib we are adoption only supports swagger 2.0(as stated in the go-openapi readme page) and does not have clear plan to support it.

Planning to switch from go-openapi to kin-openapi

[amyXia1994]

kcl-openapi should support openapi v3 since kubernetes provides v3 spec:
https://github.com/kubernetes/kubernetes/tree/master/api/openapi-spec

[benke33]

Hi,

We've (@tridentsx & me) created a program that takes a OpenAPI 3.x schema (no 3.1 yet) and converts it to KCL schemas.
This could be used until there's official support in KCL for 3.x.

Might also be used as an starting-point or inspiration for the actual support in KCL.

Link to repo: https://github.com/tridentsx/oas2kcl