| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Allow policyfile feature to be enabled in config | danielsdeleo | 2014-01-22 | 1 | -1/+5 |
| | | |||||
| * | Add Policyfile-based policy builder for chef-client | danielsdeleo | 2014-01-22 | 1 | -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 file | danielsdeleo | 2014-01-21 | 1 | -202/+3 |
| | | |||||
| * | Add indirection to allow switching policy builder implementations | danielsdeleo | 2014-01-21 | 1 | -155/+161 |
| | | |||||
| * | Add tests for public api to PolicyBuilder | danielsdeleo | 2014-01-14 | 1 | -1/+3 |
| | | |||||
| * | Add license header to policy_builder file | danielsdeleo | 2014-01-14 | 1 | -0/+21 |
| | | |||||
| * | Extract policy building concerns from Chef::Client | danielsdeleo | 2014-01-14 | 1 | -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. | |||||
 |
index : delta/ruby-gems/chef.git | |
| github.com: opscode/chef.git |
| summaryrefslogtreecommitdiff |