| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
more rubocop fixes
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
fixes:
Lint/UnreachableCode
Lint/NonLocalExitFromIterator
Lint/LiteralInCondition
Lint/EmptyEnsure
Lint/DefEndAlignment
Lint/CircularArgumentReference
|
|/
|
|
|
| |
This cookbook metadata uses the supports method, which currently parses versions
using the cookbook version parser, when it should be using the platform parser.
|
| |
|
|
|
|
|
|
|
|
| |
- multipackages dpkg_package
- fixes edge conditions in load-current-resource around purging/removing
packages that threw errors before
- fixes the ability to purge packages that have been removed
- adds a lot of functional tests for dpkg_package
|
|\
| |
| | |
Fixing Issue #2513 - the broken render of nested partial templates
|
| |
| |
| |
| |
| |
| | |
variables
Authors: Kaushik C <kaushik.chand@gmail.com>, Sam Dunne <sam@sam-dunne.com>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
adds:
- cookbook_name
- recipe_name
- recipe_line_string
- recipe_path
- recipe_line
- template_name
- template_path
accessible both as instance var (@-) and method (bare), like @node/node.
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
sure it didn't load by creating a global module inside the LWRP
and checking it outside
|
|
|
|
|
|
| |
I got confused running git on the tester with my last commit for #3101.
This should clean it up.
|
|\
| |
| | |
Reduce size of json nested entries
|
| |
| |
| |
| |
| |
| |
| |
| | |
On FreeBSD 10.1 i386 we're seeing rspec 3.2.2 raise SystemStackError if the expect line has
a nested hash of 255 levels. I'm going to guess we don't even need this many. I lowered this
test from 1000 to 300 arbitrarily some time ago.
Fixes #3101
|
|/
|
|
| |
also wire them up through the Chef class.
|
|
|
|
|
|
|
|
|
|
|
|
| |
broken by merging #2431. code was actually broken and the specs
were broken, not sure how it got into ready-to-merge in that state.
rolled back the FileUtils.rm_rf that was in the original patch since
it trashed my chef git repo and in light of:
https://github.com/ValveSoftware/steam-for-linux/issues/3671
i think the rm_rf is a bad idea.
|
|
|
|
| |
Signed-off-by: Vasiliy Tolstov <v.tolstov@selfip.ru>
|
| |
|
| |
|
|
|
|
| |
Note -- This test fails
|
|\
| |
| | |
knife upload fails due to "wrong" ruby syntax in files/* file
|
| |
| |
| |
| |
| | |
Chef should not be concerned with Ruby syntax in files delivered through the
`cookbook_file` provider.
|
|\ \
| | |
| | | |
RFC 17 implementation
|
| |/
| |
| |
| |
| | |
Conflicts:
spec/unit/cookbook_version_spec.rb
|
|\ \
| | |
| | | |
[CHEF-672] load library folder recursively
|
| |/ |
|
|\ \
| | |
| | | |
Don't override LWRP resources or providers anymore in Chef 12.
|
| |/ |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
| |
* Make the dscl user provider password handling idempotent.
* Refactor / modernize dscl user provider unit tests.
* Functional tests for dscl user provider.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://tickets.opscode.com/browse/CHEF-2923
When running `knife cookbook upload SPECIFIC_COOKBOOK`, errors in
metadata files for unrelated cookbooks should not be raised; however, we
must evaluate the metadata for all cookbooks in order to allow the
metadata `name` attribute to be different from the cookbook directory's
basename. Therefore, we must tolerate errors in metadata.rb and re-raise
them only when attempting to load the cookbook with the invalid
metadata.
|
|
|
|
| |
Fixes CHEF-3307
|
|
|
|
| |
templates directory are considered in syntax checks
|
| |
|
|
|
|
|
|
| |
This evaluates the code in a context similar to what Chef does when
compiling recipes, so that idioms like using `return` to end evaluation
of a recipe will work.
|
|
|
|
| |
In the case that a standalone cookbook exists that is using bundler, a large amount of gems can be added to the current directory. This commit reads the chefignore file and avoid having to scan through the ruby files that are in the bundler created gems directory.
|
|
|
|
|
|
|
|
| |
Now that Chef properly supports a package `response_file` using
`Chef::Resource::Template`, the Package resource should implement the
`response_file_variables` method so that variables do not have to exist
as node attributes (eg - for seeding DB passwords for configuration
files generated by packages).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reported in CHEF-4571. The recipes component of cookbook version
metadata (cbv.metadata.recipes) serialized to JSON with duplicate keys
if a metadata.rb was present that provided a recipe line matching the
cookbook name (providing a description for the default recipe).
The root cause is the behavior of the JSON serialized when called on a
hash containing matching string and symbol keys. For example:
chef > {"key1" => "sam", :key1 => "wat"}.to_json
=> "{\"key1\":\"sam\",\"key1\":\"wat\"}"
So the specific fix is to prevent inserting a symbol key for the
recipe name.
|
|
|
|
|
|
| |
- some of these have deliberate whitespace/line-ending differences
- without going through them one by one its safer to revert the lot of
them
|
| |
|
| |
|
| |
|
| |
|