| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
execute resource. Even tough this attribute is not being honored by any
provider, some existing cookbooks are still depending on this attribute.
Restore path attribute in execute resource with a deprecation message
that it will be removed in Chef 13.
|
|
|
|
|
|
|
|
|
|
|
| |
- Warning on incorrect usage of the command resource in any script
resource
- Warning on code in script resource being nil
- Specs added to force deprecation of incorrect usage in Chef-13
- Specs added around the (supported) incorrect usage in Chef-12
- Cleanup+Modernization of providers and specs
- Fixed some global state bugs around the Chef::Log.level in the spec
tests
|
|
|
|
|
| |
makes resource and provider class resolution more dynamic.
begins deprecation of Chef::Platform static mapping.
|
|
|
|
| |
to be able to warn users correctly when they configure a guard_attribute but use a ruby block in the guard.
|
|
|
|
|
|
| |
interpreter for the execute resource to be :execute.
This ensures that attributes of the resource like :environment & :cwd can be inherited by the guard when guard is specified as a string.
|
|
|
|
| |
backed by any providers.
|
| |
|
| |
|
| |
|
|
|
|
| |
The opscode/chef repository now only contains the core Chef library code
used by chef-client, knife and chef-solo!
|
|
|
|
| |
all with proper deps
|
| |
|
|
|