#chef

should policy.lock.json files be in source control?

For `policies/`-ish policies, yes

For test policies used in cookbooks, no.

Similar rules as to berks or gemfile lock.

got it, thanks

So I have an interesting problem -- I am trying to call an application via mixlib-shellout, and the application has a config file in $HOME/.config/ -- but when I try to run the application via test kitchen (vagrant), the application doesn't see the config file because kitchen uses `sudo -E` and doesn't look in /root/.config -- it looks in

/home/vagrant/.config instead.

Any ideas on what I can do to work around this?

Do I need to override the environment variable for $HOME in my mixlib-shellout call?

Majost: Yes, or if you have poise around, the poise_shell_out helper does this automatically

It's on my list to backport to shellout at some point, there is an open ticket

Sweet!

It also sets $USER and $LOGNAME, and fills in primary groups, but that's almost always the right thing anyway

Can I call new on Poise::Utils::ShellOut to check the return status?

No? They work just like Chef's normal shell_out and shell_out helpers

You either include them as a mixin or call them as global methods

Using them as globals will disable the windows command reparse though

The return value of both is the mixlib::shellout object, you can check the return codes there

oh, that works

And they are already included in most poise scopes

(resources, providers)

for the Env Policy slide on https://yolover.poise.io/ does that mean i'll end up with policies like _prod_app.rb and _dev_app.rb ?

fletchowns: No, envs become policy groups, its all discussed in there :P

ahh yup i see it

lol @ vandelay reference in yolover-example repo