KCL vet command doesn't work on schemas which import other KCL Packages

[anshuishere]

Bug Report

1. Minimal reproduce step

# Create a KCL Schema which depends on other KCL Package

import microserviceA.schema as msA
import micorserviceB.schema as msB

Schema TopLevel:
    microserviceA: msA.schema
    microserviceB. msB.schema


Where microservices are any kcl pages you include as dependencies

# Do a KCL validation

kcl vet config.yaml top-level-schema.k --forat yaml

It will fail because KCL vet will not make KCL pull the required deps or even resolve it from local cache in .kpm

2. What did you expect to see?

kcl vet works because I can do kcl run and it executes everything.

3. What did you see instead

kcl vet fails

4. What is your KCL components version?

0.10.10-linux-amd64

[He1pa]

I tried with
a.k

import b

schema Person:
    name: b.Name    

b.k

schema Name:
    name: str

a.yaml

name:
  name: "a"

kcl vet a.yaml a.k --format yaml

It worked for me on v0.11.1

Can you test with latest version and provide more details?

[anshuishere]

Let me show you an example!

I created a new KCL package called "a"

# cat kcl.mod
[package]
name = "a"
edition = "v0.11.0"
version = "0.0.1"

[dependencies]
k8s = { oci = "oci://ghcr.io/kcl-lang/k8s", tag = "1.31.2" }

# My schema.k
import k8s.api.apps.v1
schema MySchema: 
    myPodYaml: v1.Deployment

# I created a yaml to validate
myPodYaml:
   apiVersion: apps/v1
   kind: Deployment
   metadata:
     labels:
       app: mydeploy
     name: mydeploy
   spec:
     replicas: 1
     selector:
       matchLabels:
         app: mydeploy
     template:
       metadata:
         labels:
           app: mydeploy
       spec:
         containers:
         - image: myimage
           name: myimage

Now when I do validation

However kcl run command works perfectly fine

Here is the content of main.k

import yaml
import file

_filepath_input = option("input-file-path",type='str', required=True,default="myYaml.yaml")
_file_input = yaml.decode(file.read(_filepath_input))

myConig = MySchema{
    **_file_input
}

[zong-zhe]

Hi @anshuishere 😄

Thanks for your feedback! This is a feature enhancement of vet tools that allows vet tools to support package management tools, and I have opened an issue to track this feature, which will be released in the next release. Thank you again for your feedback, it is very important to us.

[anshuishere]

Another similar use case is when I have 2 schemas in the same kcl package, the import statement is not implicit. @zong-zhe

For example in example you gave above @He1pa

b.k

schema Name:
    name: str

if we use
a.k

schema Person:
    name: Name

I expect to not need to import b and use it as b.k

Seems like KCL language server is able to resolve it for IDEs as well as kcl run . works. Just not kcl vet