#chef

Eulipion: right now, chef wins. since (obviously?) what's in chef is what's actually running on the servers.

Eulipion: if I'm going to let git win, I need to prevent cookbooks and data bags from getting into chef that aren't in git.

knife-fork with the git plugin seems like it might do that for cookbooks, but I'm not sure if it has any handling for data bags in git

err, -spork

juliancdunn: I actually tried that too, unsuccessfully.

i want to echo line ot stdout during chef-solo run

hi

Dairenn: that's weird, that's what I've always used, and what the ChefSpec docs say

maybe open an issue on ChefSpec

It didn't work until I Literally added the hashed field it was phantom receiving from somewhere...

wow

:-/

Is there a way to see on a chef master somewhere, past changes a chef-client run has made?

for a node?

Anyone?

deviantlinux: If you use the premium Chef features, it gets uploaded to Analytics

coderanger: Not sure about premium features, but we run Chef Enterprise 11.x

with nothing added to it

deviantlinux: That should have Chef Analytics but an older version

coderanger: where do you see the analytics? All I see that is useful is the status page, where you can see the last check ins

deviantlinux: You would have to talk to your sales rep to see if it was included in your install, you would see an Analytics tab (might have been called Reporting back then)

coderanger: gotcha, thanks