Issue Navigator

See history of all users logged in and what they did (servers and users)

Chef should always print stderr and stdout when a shelled-out command fails

json_class should be purged from the REST API

Knife data bag from file returns a 403 if the data bag doesn't exist

Check for first-boot.json when registering a node for the first time

Cookbook uploading does not honor proxy settings

Add a config alias for user_name => node_name and api_key => client_key

recipe cannot start or restart chef-client service on SuSe. Works ok on CentOS

default attributes and environment attributes seem to be merged

template file being generated with zero bytes - checksum thinks file is correctly populated (Adam Jacob looked at this and said to submit a ticket)

"Unexpected form for PKGNAME variable" installing packages on FreeBSD 9

subscribing to a resource defined in an included recipe fails

Chef client memory baloons

Setting user for execute resource on Windows doesn't run as that user

Omnibus installation doesn't work if rvm is loaded by the root user

execute resources with action :nothing do not run on template notification with windows and chef 10.16.2

chef-client does not flush /var/log/chef/client.log as it's running as a daemon and has been run for a few days

fog and nokogiri gems are not installed anymore on windows instances starting with chef version 10.16.6

chef-client segfaults and leaves zombie

Chef-Apply does not work with template resources

bookshelf when run on remote host via knife bootstrap defaults to chef-server's non-resolving hostname, knife bootstrap --help yields no overrides.

chef-client.msi windows with 64bit ruby inside

knife download fails on chef 11

Rubigen for generating chef repositories, cookbooks and recipes

Support package, service and zfs resources on opensolaris

Add support for OpenBSD to chef-client

Resources should have a retry option to configure the number of retries when running a command failed

chef-client should verify the server's public/private? key.

Alert user if knife config doesn't include a cookbook_path

resource action should have higher precedence than only_if/not_if

If a deploy fails after the source is checked out, it is never completed in subsequent runs

Rug provider - suse support

search results for many nodes consumes large amounts of memory

Unambiguous error messages on timeouts

Add support for http_proxy environment variables to chef_client and knife

knife cookbook site vendor should use scm resource/provider

files with + in the name don't work in cookbooks

broken direct access to ohai attributes in attribute files

There are no cucumber features for knife

One-line chef-install-head script (c.f. RVM)

include_attribute on a cookbook which is not defined as a dependency should notify the user of this fact

Chef should retroactively set the log level to debug on failure

File Resource Checksums Files Indiscriminately

chef-client doesn't appear to be recognizing version numbers correctly when they use a date

Definitions in different cookbooks interact

Error message should indicate Solr is down getting connection refused from Solr

re-opening resources should be explicit or at least log a warning

Make remote_file avoid downloading a file if it hasn't changed

Define a standard directory to store notification handlers, and load them automatically