| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
Style/NegatedWhile
Style/ParenthesesAroundCondition
Style/WhileUntilDo
Style/WordArray
Performance/ReverseEach
Style/ColonMethodCall
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
4174 Style/SpaceInsideHashLiteralBraces
1860 Style/SpaceAroundOperators
1336 Style/SpaceInsideBlockBraces
1292 Style/AlignHash
997 Style/SpaceAfterComma
860 Style/SpaceAroundEqualsInParameterDefault
310 Style/EmptyLines
294 Style/IndentationConsistency
267 Style/TrailingWhitespace
238 Style/ExtraSpacing
212 Style/SpaceBeforeBlockBraces
166 Style/MultilineOperationIndentation
144 Style/TrailingBlankLines
120 Style/EmptyLineBetweenDefs
101 Style/IndentationWidth
82 Style/SpaceAroundBlockParameters
40 Style/EmptyLinesAroundMethodBody
29 Style/EmptyLinesAroundAccessModifier
1 Style/RescueEnsureAlignment
|
|
|
| |
Generated via git ls-files | xargs perl -pi -e "s/(Author.*?<[^@]+@)(?:opscode\\.com|getchef\\.com)(>)/\\1chef.io\\2/gi"
|
|
|
| |
Generated via git ls-files | xargs perl -pi -e "s/[Cc]opyright (?:\([Cc]\) )?((?\!$(date +%Y))\\d{4})(-\\d{4})?([, ][ \d]+)*(,|(?= ))/Copyright \\1-$(date +%Y),/g"
|
| |
|
|
|
|
|
|
|
| |
This is an entirely mechanically generated (chefstyle -a) change, to go
along with chef/chefstyle#5 . We should pick something and use it
consistently, and my opinion is that double quotes are the appropriate
thing.
|
|
|
|
| |
chefstyle -a fixed 1044 occurrances
|
|\
| |
| | |
don't blow up when json object has no recipes
|
| |
| |
| |
| | |
fixes loading brand new node objects from json
|
| |
| |
| |
| | |
useless use of `"#{foo.to_s}"`
|
|/
|
|
|
|
|
| |
In the process, stop auto-expanding JSON in the HTTP client, and let
individual classes control that themselves.
Fixes #2737, Fixes #3518
|
| |
|
|
|
|
|
|
|
| |
previously if the node had a { normal: { tags: nil } } that we read
since the key existed (but was nil) we would not initialize with an
array. replacing the code with a call to node.set_unless revealed that
set_unless was similarly buggy. fixed both issues by fixing set_unless.
|
|\
| |
| | |
Use the initializer to avoid NoMethodError on nil.include?
|
| |
| |
| |
| | |
Rename the argument so as to not collide with the tags method.
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
| |
Prior to chef 12.2 we included unexpanded 'cookbook' names for default
recipes. In 12.2, we moved to expanded ('cookbook::default') names,
which broke some searches.
However, some of our users have now moved to searching for expanded,
so we need to cater for both.
Fixes #3767
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* fix node[:recipes]
* add node[:expanded_run_list]
* add node[:cookbooks]
|
| |
|
|
|
|
|
|
|
| |
with validation off any bad utf8 data will not cause the
ffi-yajl encoder to raise. with ffi-yajl >= 2.2.0 the bad
data will be scrubbed to produce valid JSON to POST/PUT to
the server.
|
|
|
|
| |
Should close [Issue 2863](https://github.com/chef/chef/issues/2863)
|
| |
|
| |
|
|
|
|
|
|
| |
- adding rm, rm_default, rm_normal, rm_override APIs
- adding default!, normal! and override! APIs
- changing force_default! and force_override! APIs
|
| |
|
|
|
|
|
|
|
|
|
| |
should fully convert to using ffi-yajl
there are still issues with JSON gem monkeypatching interacting with
chef-zero and the spec tests so we keep the requires here for the
json gem and the ffi_yajl/json_gem here. when ohai and chef-zero are
fixed, we an just require ffi_yajl.
|
|
|
|
| |
This reverts commit adbb0fa85cc45b93ba91dc3019094b312cafb35c.
|
| |
|
| |
|
| |
|
|
|
|
| |
environment names to empty strings
|
|\
| |
| |
| |
| | |
Conflicts:
lib/chef/client.rb
|
| | |
|
| |
| |
| |
| |
| |
| | |
this makes it so that the recipes in the attribute will be fully
qualified, and will avoid the problem of both "cookbook" and
"cookbook::default" showing up.
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
| |
As per Dan's suggestions, use a primary run_list and an override, and
take care to ensure that the correct one is used to save the node.
|
|
|
|
|
|
| |
This commit adds a simple <=> method which will allow for Chef::Node
objects to be ordered based on their name. The primary use case is
sorting arrays of nodes for use in templates.
|
| |
|
|
|
|
| |
In all of github there is not a single cookbook using this.
|
|
|
|
|
| |
Also, coerce node[:recipes] to an Array so that Node#recipe? will work
correctly when the recipes attribute has not been set.
|