kcl-lang/kcl

Feature Request Is your feature request related to a problem? Please describe: There is no methods for interracting with file specific version selection. Describe the feature you'd like: We are building small config processors on top of KCL where we use non KCL files as assets (json or yaml files or other) to populate new object or trigger a specific operation. And sometime we want to handle versionning directly in our KCL declaration. Lets consider we are in the configs directory managed by git, where json assets files are used as part of our KCL config definition, but we want to leverage git versionning to select the version we want and better manage our configs changes. It would be nice to be able to natively use tags, or commit hash to select a specific asset file version. Describe alternatives you've considered: We built a plugin for that, laveraging python and the gitpython package and create a small function for it (snipet below) import os import logging import hashlib from pat

Hi! 👋 Your repo currently scores L1 · Assisted · 1/10 on the AI Codebase Maturity Model — a 5-level framework (L1 Assisted → L5 Self-Sustaining) that measures how ready a codebase is for AI-assisted engineering. See your full scan 👉 console.kubestellar.io/acmm?repo=kcl-lang/kcl The dashboard shows every detected vs. missing criterion, with an "Ask agent for help" button that launches an AI mission to add any missing one. Add a badge to your README Paste this in your README to show your ACMM level — it updates automatically as you add criteria: [](https://console.kubestellar.io/acmm?repo=kcl-lang%2Fkcl&utm_source=github&utm_medium=issue&utm_campaign=acmm-outreach) Why it matters Projects with higher ACMM scores get measurably better AI-assisted PRs because the agent has rules, tests, and metrics to work against. The badge signals to contributors (

We built a guided install mission for KCL inside KubeStellar Console, a standalone Kubernetes dashboard (unrelated to legacy kubestellar/kubestellar, kubeflex, or OCM — zero shared code). Open the KCL install mission What the mission does The mission runs against your live cluster via kubeconfig. Each step: Pre-flight — checks prerequisites (curl or Homebrew) Commands — shows the exact install commands with flags explained. Copy-paste or run directly from the console Validation — after each step, queries the cluster to verify success (pod phase, CRD registration, service endpoints) Troubleshooting — on failure, reads pod logs, events, and resource status from your cluster and suggests fixes Rollback — each step includes the corresponding uninstall commands to undo Works as read-only documentation too — no cluster connection required to browse. Architecture graph LR A["KubeStellar Console"] --> B["30+ Dashboards<br/>150+ Monitoring Cards"] A -->

Enhancement 当前kcl执行仅支持输出json和yaml格式，目前项目中遇到期望输出jsonschema, xml等多种类型格式，当前开源代码存在如下问题： 不管是否使用json或yaml格式，每次执行时必定会进行翻译生成，即使只用其中一种格式，也会生成输出，浪费了计算成本。 当前协议接口中固定了输出格式为json和yaml两种，无法进行灵活扩展。即使对runtime中扩展了新的格式生成器也无法直接使用。 对社区建议： kcl命令行支持--format命令，用于指定编译kcl源码执行后生成格式，使用示例如下： kcl [run] --format [yaml|json|...] hello.k 针对--format描述通过kcl run -h展示 --format string Specify the output format (default "yaml") kcl的前后端通信协议扩展gpyrpc.proto中，对ExecProgram_Result结构进行改造，支持扩展兼容： 将result_yaml和result_json修改为out_format和out_message 当--format=json时，out_format