summaryrefslogtreecommitdiff
path: root/lib/chef/policy_builder.rb
Commit message (Collapse)AuthorAgeFilesLines
* Remove copyright dateslcg/remove-copyright-datesLamont Granquist2020-04-131-1/+1
| | | | | | | | Legally incredibly dubious, particularly since we don't follow it strictly as policy, and we have git history instead, which does it right. This is just a waste of time and a cargo cult. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Convert require to require_relativeLamont Granquist2019-05-081-3/+3
| | | | | | | This gives a speed boost since rubygems does not have to scan through every gem in the gemset in order to find the file. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Update all auth email address from opscode.com and getchef.com to chef.io.Noah Kantrowitz2016-02-021-1/+1
| | | Generated via git ls-files | xargs perl -pi -e "s/(Author.*?<[^@]+@)(?:opscode\\.com|getchef\\.com)(>)/\\1chef.io\\2/gi"
* Copyright year update for 2016 and massive cleanup.Noah Kantrowitz2016-02-021-1/+1
| | | 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"
* Use double quotes by defaultThom May2016-01-141-3/+3
| | | | | | | 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.
* Use the dynamic policy builder everywheredanielsdeleo2015-09-171-8/+0
|
* Add Dynamic PolicyBuilder to switch on policyfile modedanielsdeleo2015-09-171-0/+1
| | | | | | 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.
* Allow policyfile feature to be enabled in configdanielsdeleo2014-01-221-1/+5
|
* Add Policyfile-based policy builder for chef-clientdanielsdeleo2014-01-221-0/+1
| | | | | | | | | | | | NB: This is experimental and a bit of a hack. There is no server-side support, so interactions with the server are coded in a "compatibility mode" using data bag items and Chef 11 style cookbook version APIs. The Policyfile PolicyBuilder uses a single document from the server as the authoritative cookbook version set and expanded run list. Enabling it will disable support for environments and roles. In addition, chef-solo and override run lists are currently unsupported, though they could be supported in the future.
* Extract "expand node" policy builder to new filedanielsdeleo2014-01-211-202/+3
|
* Add indirection to allow switching policy builder implementationsdanielsdeleo2014-01-211-155/+161
|
* Add tests for public api to PolicyBuilderdanielsdeleo2014-01-141-1/+3
|
* Add license header to policy_builder filedanielsdeleo2014-01-141-0/+21
|
* Extract policy building concerns from Chef::Clientdanielsdeleo2014-01-141-0/+214
Chef::Client has too many responsibilities that are difficult to test in isolation. Refactor them out to an implementation class. This is a prerequsite for providing alternative policy building strategies.
View Lorry Controller Status