You are currently using a new, unsaved search.
Ability to decouple application environment from chef_environment
Environment existing settings are not displayed correctly when editing environments or nodes via the WebUI
Support for enviroment attributes in roles: env_default_attributes and env_override_attributes
Chef WebUI reveals environment select box list on failed user logins
"knife status" ignores specified -E environment
chef-client -E options ignores single lettered named environments
Hosted Chef WebUI doesn't filter node status environment using selected environment
Knife bumps the cookbook version in environment even there was an error while uploading
default attributes and environment attributes seem to be merged
Supporting checksums as cookbook version constraints
knife ec2 server create -E staging does not assign the node to the staging environment
not_if/only_if does not honor script resource's environment
Allow cookbook versions on _default environment
knife environment list `<class:Environment>': uninitialized constant Chef::Mixin::FromFile (NameError)
Closed
Confirmed
Open
