2:58 AM
grzm I’m working with the pod.babashka.aws pod and it’s very noisy with logging statements (via clojure.tools.logging). Is there a way to silence these logs? If this were straight up clojure, I’d do something along the lines of -Dclojure.tools.logging.factory=clojure.tools.logging.impl/disabled-logger-factory. I see I can set Java system properties that are read by babashka using -D, but I suspect they’re not being passed to the pod? The more likely case is I’m just Doing it Wrong™.
10:17 AM
borkdude @grzm There is a workaround for this. You can start the pod using the filename instead of the qualified symbol and then pass "-Dclojure.tools.logging.factory=clojure.tools.logging.impl/disabled-logger-factory" as an argument to it
10:17 AM
I think we could support this better by allowing to pass :command-line-args or so via the options
2:58 AM grzm I’m working with the pod.babashka.aws pod and it’s very noisy with logging statements (via clojure.tools.logging). Is there a way to silence these logs? If this were straight up clojure, I’d do something along the lines of -Dclojure.tools.logging.factory=clojure.tools.logging.impl/disabled-logger-factory. I see I can set Java system properties that are read by babashka using -D, but I suspect they’re not being passed to the pod? The more likely case is I’m just Doing it Wrong™. 10:17 AM borkdude @grzm There is a workaround for this. You can start the pod using the filename instead of the qualified symbol and then pass "-Dclojure.tools.logging.factory=clojure.tools.logging.impl/disabled-logger-factory" as an argument to it 10:17 AM I think we could support this better by allowing to pass
:command-line-argsor so via the options