Closed markphillips100 closed 8 months ago
Hello @markphillips100
Thank you for your feedback. This may be a bug in the kcl-openapi tool https://github.com/kcl-lang/kcl-openapi, which changes the default value to go map string instead of KCL dict string. The correct code at line 1171 may be
readinessChecks?: [ApiextensionsCrossplaneIoV1CompositionSpecResourcesItems0ReadinessChecksItems0] =[{matchCondition: {status: True, type: "Ready"}, type: "MatchCondition"}]
Yes that gives no errors. I'm assuming then that kcl import is just a wrapper over kcl-openapi?
I'll raise the issue there then. Feel free to close.
May I ask what version of kcl-openapi the kcl 0.8.0 version uses? If there is a later version I may try that direct just to see if the issue remains in latest code from that repo.
I think this issue still exists in the latest version.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
kcl mod init mymod
andcd mymod
.kcl import -m crd -s -o . <location of yaml from step 1>
main.k
contents with the following code:kcl run
from module folder.2. What did you expect to see? (Required)
No errors.
3. What did you see instead (Required)
4. What is your KCL components version? (Required)
KCL: 0.8.0-windows-amd64 KCL vscode extension: v0.1.5 OS: Windows11