You are currently using a new, unsaved search.
Chef should set a timeout for yum-dump
resource action should have higher precedence than only_if/not_if
ifconfig provider for debian/ubuntu platforms
Delayed attribute evaluation
11: Make git provider respond to a new repo URL
Overriding duplicate definition *
chef-apply ignores all command line flags
The config file's path isn't shown in exceptions
Update Reporting Client Protocol
usermod for changing groups on SmartOS should use -G
Monkey Patch Dir.rb exception on windows
Monkey patching Dir makes Windows sad :'(
Rubygems 2.0 heuristic is incorrect on some environments upgraded from rubygems 1.8
remote_file source "downloaded from" is empty, but works
remote_file does not support why-run correctly
chef-client ignores port specification in an HTTPS URL
remote_file gives deceptive error message replacing remote_file of running process
File provider follows symlinks; Template provider does not (security implications and inconsistency)
File providers in whyrun branch need cleanup in how they handle tempfiles
Define helper functions on template resource
File Provider Refactor
Make remote_file avoid downloading a file if it hasn't changed
remote_file should respect ETags
include etags, last-modified, expires and cache-control header handling in Chef::REST
When the file / template has a hardcoded path defined (either set via node attribute or hard coded as in the example), the notifies parameter does not work.
Notifications from remote_file resource not working on windows
execute resources with action :nothing do not run on template notification with windows and chef 10.16.2
I cant install an aplication on a server
Daemonized chef-client should fork before a chef run
resource "file" is non-idempotent when specifying file mode in combination with a non-existing user
chef-client never runs again after an http timeout to the chef server.
Deploy resource/provider should allow for custom config directories
Files managed via template resources are updated unnecessarily