| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
Created via git ls-files | xargs perl -pi -e "s/(Copyright.*?), Opscode(,)? Inc(\.)?/\\1, Chef Software Inc./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"
|
| |
|
|
|
|
| |
See chef/chefstyle#11 for analysis and discussion. We select '{}' since
audit of our source code shows that is the most common, and that used to
be the dominant learning paradigm (e.g. in ruby 1.9 pickaxe book.
|
| |
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
list expansion trace.
Added event to report expanded run list
Updated json conversion to use chef compat json.
Remove RunListExpansion from JsonCompat
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
fixes #3618
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
fix deprecation warnings
|
| | |
|
|
|
The opscode/chef repository now only contains the core Chef library code
used by chef-client, knife and chef-solo!
|
