Open jayhendren opened 7 years ago
Eh, given the kind of nonsense in a normal kitchen output, this never really bothered me much.
BTW, even if I explicitly set log_level
in transport section I still see that kitchen-sync pollutes output of converge stage:
.kitchen.yml
transport:
name: sftp
log_level: error
kitchen-sync seems to have a bug with reading log_level
properties. There is no way to change that value. See kitchen diagnose
and you will see, that log_level
is always :info
no matter what you've set in .kitchen.yml
.
There is not currently any such thing as a log level setting for the transport, but there could be.
Eh, given the kind of nonsense in a normal kitchen output, this never really bothered me much.
This is not normal kitchen output. What other output shows ruby object level details as part of normal output?. This is debug level information and should be classified accordingly.
Eh, given the kind of nonsense in a normal kitchen output, this never really bothered me much.
Yes but the normal output is useful in debugging my recipes. The 10 lines of SFT information is only useful in debugging this Gem. It's enough to make me simply not use it.
When uploading files with the SFTP transporter, my testkitchen output gets polluted with a lot of this kind of stuff:
Should this perhaps be debug output instead of info output?