Jira (BOLT-263) log bolt results to a log file

[Michal Ruzicka (JIRA)]

Title: Message Title

Michal Ruzicka commented on BOLT-263   Re: log bolt results to a log file Yasmin Rajabi, for instance with this configuration in my ~/.bolt/debug.log: --- log: console: level: :info ~/.bolt/debug.log: level: :debug append: false running the following command: bolt command run 'cat /etc/hosts' --nodes 172.16.0.52 --user root --no-host-key-check --debug --format json produces the following output in the terminal: 2018-03-05T23:05:31.657255 DEBUG Bolt::Inventory: Did not find 172.16.0.52 in inventory 2018-03-05T23:05:31.657399 DEBUG Bolt::Inventory: Did not find any variables for 172.16.0.52 in inventory { "items": [ 2018-03-05T23:05:31.761632 DEBUG Bolt::Transport::SSH: Authentication method 'gssapi-with-mic' is not available 2018-03-05T23:05:31.762185 DEBUG Bolt::Transport::SSH: Running command 'cat /etc/hosts' on 172.16.0.52 2018-03-05T23:05:31.859484 DEBUG 172.16.0.52: Opened session 2018-03-05T23:05:31.859597 DEBUG 172.16.0.52: Executing: cat /etc/hosts 2018-03-05T23:05:32.045656 DEBUG 172.16.0.52: stdout: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6   2018-03-05T23:05:32.046018 DEBUG 172.16.0.52: Command returned successfully 2018-03-05T23:05:32.046164 DEBUG 172.16.0.52: Closed session {"node":"172.16.0.52","status":"success","result":{"stdout":"127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4\n::1 localhost localhost.localdomain localhost6 localhost6.localdomain6\n","stderr":"","exit_code":0}} ], "node_count": 1, "elapsed_time": 0 } I.e. the actual JSON output mixed with log messages (all of them accidentally at the DEBUG level). At the same time all of the log messages are (in accordance with the configuration) also written to the ~/.bolt/debug.log file, and since the file was configured not to be appended to, its contents is exactly: 2018-03-05T23:05:31.657255 DEBUG Bolt::Inventory: Did not find 172.16.0.52 in inventory 2018-03-05T23:05:31.657399 DEBUG Bolt::Inventory: Did not find any variables for 172.16.0.52 in inventory 2018-03-05T23:05:31.761632 DEBUG Bolt::Transport::SSH: Authentication method 'gssapi-with-mic' is not available 2018-03-05T23:05:31.762185 DEBUG Bolt::Transport::SSH: Running command 'cat /etc/hosts' on 172.16.0.52 2018-03-05T23:05:31.859484 DEBUG 172.16.0.52: Opened session 2018-03-05T23:05:31.859597 DEBUG 172.16.0.52: Executing: cat /etc/hosts 2018-03-05T23:05:32.045656 DEBUG 172.16.0.52: stdout: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6   2018-03-05T23:05:32.046018 DEBUG 172.16.0.52: Command returned successfully 2018-03-05T23:05:32.046164 DEBUG 172.16.0.52: Closed session I.e. only the log messages, but not the JSON result. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.