New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chefctl on Chef 16 on macos does not result in colored output #78
Comments
My guess is that Chef is doing more work to determine when it's output is being piped, and because we're a pipe it's going "aw shit, best not send colors!" If you update your chefctl config and add |
btw, I'm keeping up with bleeding edge 15 but have not started testing 16 yet, mostly because I'm still watching the fun string of bugs and bugfixes :) I'll probably try out 16 in a month or so. |
(also, for the purposes of testing, |
|
Interesting. I'm happy to setup 16 somewhere, but I don't have access to osx. Is this reproducible on linux? |
I haven't tried on Linux yet since we haven't started testing chef 16 on non-macOS.
Thanks,
Erik Gomez
…________________________________
From: Phil Dibowitz <notifications@github.com>
Sent: Wednesday, June 3, 2020 1:16:21 PM
To: facebook/chef-utils <chef-utils@noreply.github.com>
Cc: Erik Gomez <e@eriknicolasgomez.com>; Author <author@noreply.github.com>
Subject: Re: [facebook/chef-utils] chefctl on Chef 16 on macos does not result in colored output (#78)
Interesting. I'm happy to setup 16 somewhere, but I don't have access to osx. Is this reproducible on linux?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#78 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABLL6GA77WJYK2S6ENP46PDRU2HPLANCNFSM4NR3K6AA>.
|
I'm at a loss on this one, but I've noticed that chefctl does not result in colored output when using Chef 16 (Chef Infra Client: 16.1.16)
After attaching some debugging I've confirmed that
sudo chefctl -icH
is equivalent tosudo /opt/chef/bin/chef-client -l fatal -F doc --no-fork
.The only thing I can come up with is the ruby
/opt/chef/embedded/bin/ruby
has updated some gems that are prohibiting this behavior or have simply changed.The text was updated successfully, but these errors were encountered: