I would think the JVM requirement makes it a non-starter. But I could have it all wrong -- when it comes to "devops" no amount of unnecessary complexity and dependencies seem too much for some people.
I use Go and bash scripting.
I use Go and bash scripting.
You don't choose a language you fell in love with or want to learn and wedge it into the problem because you want to. Even if you can use Clojure that doesn't make it a good idea. It has too many dependencies, isn't available out of the box on typical servers, and imposes a severe limit on the people who could take over system/infra admin.
I was not commenting on the appropriateness of introducing a scripting language for devops work. I was responding to your incorrect assumption that writing scripts in Clojure would require a JVM.
If a company uses Clojure or ClojureScript already, Babashka is a fairly natural way to support devops for that company.