You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 21, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 21, 2022. It is now read-only.
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.
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.
Activity
coderanger commentedon Apr 21, 2017
Eh, given the kind of nonsense in a normal kitchen output, this never really bothered me much.
izinovik commentedon Jun 21, 2017
BTW, even if I explicitly set
log_levelin transport section I still see that kitchen-sync pollutes output of converge stage:lehn-etracker commentedon Jul 7, 2017
kitchen-sync seems to have a bug with reading
log_levelproperties. There is no way to change that value. Seekitchen diagnoseand you will see, thatlog_levelis always:infono matter what you've set in.kitchen.yml.coderanger commentedon Jul 10, 2017
There is not currently any such thing as a log level setting for the transport, but there could be.
logicminds commentedon Nov 1, 2019
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.
Fix coderangergh-33 quiet the output of sftp transfer time
Noel-Jones commentedon Jan 17, 2020
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.