You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Technically you can probably look for Chef::Config.local_mode, if you are doing chef-client -z. But I would not suggest this: we've seen if Chef::Config.solo exceptions strewn about through cookbooks, and what it really means is that when you test your cookbook, you aren't testing the cookbook that will run in production. I would use node attributes for your cookbooks to tell it credentials and such.
Thanks for the answer. I want to use these exceptions only for not having to use encrypted data bags when running test-kitchen - didn't find an easy way to distribute required .pem files into VMs during test run.
chef
locked and limited conversation to collaborators
Nov 16, 2017
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This would be useful for switching test credentials, etc. A piece of documentation about it in
README.md
would be nice.The text was updated successfully, but these errors were encountered: