| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
to_hash on a lot of these objects should go away, but even eliminating
all our calls to to_hash on these objects internally is difficult.
(e.g. converting the knife ui code to call #to_h means we wind up
calling nil#to_h which "helpfully" becomes '{}' which is hilarious and
i don't know why someone thought that was a good idea).
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
|
|
|
| |
We also now set chef_environment the same as policy group when that's
appropriate
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
| |
Signed-off-by: Jon Cowie <jonlives@gmail.com>
|
|
|
|
|
|
| |
This commit implements RFC-105 and adds specs to verify attribute hoisting is working correctly in conjunction with existing attributes.
Signed-off-by: Jon Cowie <jonlives@gmail.com>
|
|
|
|
| |
Signed-off-by: Tyler Cloke <tylercloke@gmail.com>
|
|
|
|
|
|
|
|
|
| |
This implements RFC 67, which removes cookbook segments, and moves to a
single list of all the files contained in a cookbook. This allows us to
move forward with better audit modes and also proper shipping of ohai
plugins.
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\
| |
| | |
Add the policyfile revision_id as an automatic attribute.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
/cc @coderanger @danielsdeleo
We have been looking for an easy way to get this value into our error
reporting application and it surprised me that it isn't already
captured. If there's a better way to do this totally open for thoughts!
Signed-off-by: John Bellone <jbellone@bloomberg.net>
|
|/
|
|
|
|
|
|
| |
This adds URLs to each class of deprecation, and correctly prints and
formats them for maximum user efficiency. We also provide the URL to the
data collector for Visibility to ingest.
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
|
|
| |
ie, only when we're in OG mode and not in local mode.
Signed-off-by: Thom May <thom@chef.io>
|
| |
|
| |
|
|
|
|
|
| |
this is part of our informal style guide, lets make it formal since
clearly its not getting followed very well.
|
|\
| |
| | |
RFC-060 gem metadata MVP
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
this leverages the PR:
https://github.com/bundler/bundler/pull/4245
to redirect output from bundler into chef's logger/formatter to get the
UI right. if you don't have that in the external bundler you'll just
get output on STDOUT. fix is to upgrade bundler.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
252 Style/TrailingCommaInLiteral
84 Style/TrailingCommaInArguments
15 Style/SpaceAroundKeyword
--
351 Total
We already dealt with SpaceAroundKeyword under its old name
SpaceBeforeModifierKeyword, it looks like it got stricter about
spaces after keywords.
TrailingComma also got split, and it looks like the
TrailingCommaInArguments behavior is new?
|
|\ \
| | |
| | | |
pull rubocop 0.37.2 into chefstyle
|
| | |
| | |
| | |
| | | |
this looks nicer.
|
| |/
| |
| |
| |
| | |
this is from the same ruleset that we had, but the new code catches more
conditions.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
In the process, stop auto-expanding JSON in the HTTP client, and let
individual classes control that themselves.
Fixes #2737, Fixes #3518
|
| |
|
|
|
|
|
|
|
|
|
|
| |
list expansion trace.
Added event to report expanded run list
Updated json conversion to use chef compat json.
Remove RunListExpansion from JsonCompat
|
|
|
|
| |
Some third-party tools are using this, we need it to work.
|
|
|
|
| |
Also, improve the language around unsupported features/options.
|
| |
|
|
|
|
| |
Also, mark internal public API as @private
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Now we need to switch PolicyBuilder implementations based on several
factors instead of just a single config settings, including content of
the node fetched from the Chef Server.
|
| |
|
|
|
|
|
| |
fixes the priority maps on chef-apply by wiring it up in the
constructor of the client
|
|
|
|
| |
also wire them up through the Chef class.
|
|
|
|
|
|
|
|
|
| |
Cookbook artifacts differ in these ways:
* the name field is the cookbook name instead of name+version
* there is no "cookbook_name" field
* cookbook artifacts don't have a json_class when downloaded from the
server
* there is an identifier field
|
| |
|
| |
|
| |
|