In lib/chef_apply/action/converge_target.rb, there is this code:
if c.exit_status == 0
ChefApply::Log.debug(c.stdout)
notify(:success)
I can't think of a useful case where we should require log level of debug to output the received log from the target host's run. Setting chef-apply's output to debug spits out a lot of unnecessary stuff whereas the target host's output is much more valuable.
I propose chef-apply uses Log.info instead, to reflect this higher importance of the target host output over the minutiae of the chef-apply run in itself.
Chef Apply Version
All versions up to 0.1.13, latest as of writing.
Platform Version
Arch Linux patched to latest as of writing.
Replication Case
In .chef-workstation/config.toml:
[log]
level = "info"
Run a recipe via chef-run myhost path/to/recipe.rb
Client Output
Expected: the target host's output from running the recipe is displayed or logged into a file.
Actual: no output from the target host is ever logged or displayed by chef-apply until its log level is set as low as debug, which clutters the logging a lot.
Description
In
lib/chef_apply/action/converge_target.rb, there is this code:I can't think of a useful case where we should require log level of
debugto output the received log from the target host's run. Settingchef-apply's output todebugspits out a lot of unnecessary stuff whereas the target host's output is much more valuable.I propose
chef-applyusesLog.infoinstead, to reflect this higher importance of the target host output over the minutiae of thechef-applyrun in itself.Chef Apply Version
All versions up to 0.1.13, latest as of writing.
Platform Version
Arch Linux patched to latest as of writing.
Replication Case
In
.chef-workstation/config.toml:Run a recipe via
chef-run myhost path/to/recipe.rbClient Output
chef-applyuntil its log level is set as low asdebug, which clutters the logging a lot.Stacktrace
N/A