| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
makes resource and provider class resolution more dynamic.
begins deprecation of Chef::Platform static mapping.
|
| |
|
|
|
|
|
| |
array for explicit search path manipulation. This is the backwards compatible solution to migrate away from the implicit search path in favor of making it explicit when needed (which is rarely).
Conflicts:
lib/chef/cookbook_version.rb
|
| | |
|
| |
|
|
|
|
|
| |
- Resource::Template compiles helper methods/module bodies into a
collection of modules for inclusion into the template context.
- Resource::Template checks for obvious invalid input to helper
definition methods.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds helper methods to a template via the following syntax:
```
template "name" do
# singular method definition:
helper(:method_name) { method_body }
# inline module definition
helpers do
def method_name
method_body
end
end
# external module inclusion
helpers(MyHelperModule)
end
```
In each of the above cases, variables defined by Chef (e.g., `@node`)
or the user (via `:variables => {}`) can be accessed as normal.
Could use the following improvements:
- Template partials are not supported
- Input validation on Resource::Template should be improved
- Needs Unit tests for Template provider/implementation classes
|
| |
|
|
| |
The opscode/chef repository now only contains the core Chef library code
used by chef-client, knife and chef-solo!
|
| |
|
|
| |
all with proper deps
|
| | |
|
| | |
|
| |
|
