Kusion Configuration Language (KCL) is an open source constraint-based record and functional language. KCL improves the writing of a large number of complex configurations such as cloud native scenarios through mature programming language technology and practice, and is committed to building better modularity, scalability and stability around configuration, simpler logic writing, fast automation and good ecological extensionality.

their GitHub https://github.com/KusionStack/KCLVM

I see a problem there with the pythonic range() function. I suggest to create syntax that can express closed, partially closed and open intervals. And make it always requiring two arguments.

As it is now, people have to know the quirks of python to understand what this schema wants to say. The meaning should be clear on first look.

Thank you for your suggestion. At first, we expected to make an SRE-friendly language and made enhancements in configuration and policy writing (try to be close to python and shell in use, and use some pythonic built-in functions such as range). However, this does bring additional learning costs to some users who are unfamiliar with python's usage. We will try to eliminate some of python's triks in the future to make the syntax and semantics of KCL clearer.

Recent related post (22 comments) https://news.ycombinator.com/item?id=34144566

Also: comparison with other languages such as dhall or cue or jsonnet at https://kcl-lang.io/docs/user_docs/getting-started/intro/