Controllng `dnst` log level with Cascade.

[ximon18]

The log level of Cascade can be controlled by configuration setting, command line argument or at runtime via the cascade debug change-logging command.

Log level of the invoked dnst commands however is not affected (currently) by the current Cascade log level. Should it be?

As a work-around one can instead set the dnst-binary-path config setting to point to a shell script that forcibly sets the dnst verbosity level, e.g.:

$ grep dnst-binary-path cascade.conf
dnst-binary-path = "/tmp/cascade-dnst-logged"

$ cat /tmp/cascade-dnst-logged
#!/bin/bash
dnst -v trace $*

This issue serves as a place to discuss whether we want to improve the ability to control the dnst log level when invoked by Cascade, or whether to document the above "trick" in the mean time.

The reason I came across this was the need to see in more detail what was happening when dnst keyset was connecting to a KMIP server.