clj-kondo VS tanka

My best suggestion here would be clj-kondo with flycheck-clj-kondo in Emacs. I really can't recommend it enough and would have killed to have it when I was learning Clojure. Not only will it underline all of those references to (now) undefined vars, but it can tell you about numerous little mistakes like mixing up arguments orders in (say) sequence functions, misplaced docstrings that get discarded, style conventions, etc. It's staggering how good it is even for a language as dynamic as Clojure.

The clj-kondo linters are worth reading.

Sure!

Spec: https://github.com/edn-format/edn

Example (linter config): https://github.com/clj-kondo/clj-kondo/blob/634294183a0aa2ca...

Clj-kondo doesn't produce an AST but you could easily combine the analysis output with the AST produced by rewrite-clj by matching on location.

But if you want full support, you can implement a hook: https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md

Please configure and use tools like clj-kondo and kibit. Kibit will report areas where you could write idiomatic clojure instead. Eg, it should catch all those (if (condition) true false) and ask you to replace it with (condition). Or if you really need a boolean value, use boolean to coerce it.

Try clj-kondo, a Clojure linter which will tell you about arity errors and more, before you even evaluate your code.

I would recommend implementing a similar API to Grafana Tanka: https://tanka.dev

When you "synthesise", the returned value should be an array or an object.

1. If it's an object, check if it has an `apiVersion` and `kind` key. If it does, yield that as a kubernetes object and do not recurse.

Maybe you'd like jsonnet: https://jsonnet.org/

I find it particularly useful for configurations that often have repeated boilerplate, like ansible playbooks or deploying a bunch of "similar-but" services to kubernetes (with https://tanka.dev).

Dhall is also quite interesting, with some tradeoffs: https://dhall-lang.org/

A few years ago I did a small comparison by re-implementing one of my simpler ansible playbooks: https://github.com/retzkek/ansible-dhall-jsonnet

- validation is often impractical (at least identifying exactly where the error is… I’m looking at you Helm!)

Unrelated to OP, but you can leverage Tanka to extend helm charts with functionality not provided by upstream.

https://tanka.dev/

Although jsonette might be considered more complex Tanka is a great alternative for k8s config management.

At Grafana Labs we're using jsonnet at scale, while being a powerful functional language it is also excellent for rendering JSON/YAML config. We have developed Tanka[0] to work with Kubernetes, for other purposes I can recommend this course[1] (authored by me).

[0] https://tanka.dev/

[1] https://jsonnet-libs.github.io/jsonnet-training-course/

If you're hitting the limits of Kustomize, maybe look at Tanka as well.

Yes, try Tanka.

yes. basically. and this is a path that multiple people are trying to solve. e.g. AWS CDK8s, https://tanka.dev/, etc

Compose would be awesome.

http://tanka.dev

(Note I work for Grafana Labs who fund Tanka and use it for all production config)