summaryrefslogtreecommitdiff
path: root/lib/chef/client.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add minimal ohai mode option flagminimal-ohai-modedanielsdeleo2015-03-271-1/+2
|
* We should not change how exceptions are raised if audit mode is disabledJay Mundrawala2015-03-171-1/+2
|
* Fix more incorrect terminologyJulian C. Dunn2015-03-111-1/+1
|
* Move the require up a levelRob Redpath2015-01-251-0/+1
|
* Drop the SSL warning now that we have a safe defaultPhil Dibowitz2015-01-161-33/+0
|
* Suppress SSL warnings if I know what I'm doingPhil Dibowitz2015-01-151-1/+1
|
* Unit tests for audit-mode in chef-solo.Claire McQuin2014-12-171-1/+2
| | | | | * Audits are disabled by default. * Also, updated spec file to use RSpec :let.
* if in why_run, do not enter the audit phase - because people run why_run to ↵tyler-ball2014-12-171-2/+7
| | | | see converge statistics
* Failing an audit example will now raise an error and make chef exit with a ↵tyler-ball2014-12-171-1/+2
| | | | non-zero code
* Instructions on running audit mode examples.Serdar Sutay2014-12-171-6/+2
|
* Use a central runnerClaire McQuin2014-12-171-1/+1
|
* Add a Chef::Audit::Controls object for 'controls'Claire McQuin2014-12-171-2/+14
|
* Adding audit mode JSON formattertyler-ball2014-12-171-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | First pass at DSL additions Renaming DSL methods to match the spec Creating our own example group class to simplify adding examples to the spec runner Adding logic for exceptions from converge phase not interfering with audit phase and vice-versa Adding error handling so saving node doesn't prevent us from running audit mode - decouples converge phase and audit phase more Updating for github comments Add setup phase to audit-mode. Refactor runner into own class. Fix typo tie things together Adding first round of formatter integration - STDOUT doc formatter Preparing for demo - using rspec documentation formatter for output instead of the proxy Add serverspec types and matchers. add rspec/its Add gems as core dependencies Updating with changes from demo Updating with @mcquin and @lamont comments Getting rid of unused method Wiring audit event proxy to send events correctly to the audit_reporter removing old pry debugging statement Removing unecessary todo Sending to correct server URL Fixing TODOs Adding uncaught error information
* Sending to correct server URLtyler-ball2014-12-171-3/+5
|
* Make sure we don't close the output_stream after running rspec.Serdar Sutay2014-12-171-5/+3
|
* Wiring audit event proxy to send events correctly to the audit_reportertyler-ball2014-12-171-7/+19
|
* Adding first round of formatter integration - STDOUT doc formattertyler-ball2014-12-171-3/+3
|
* Adding audit mode JSON formattertyler-ball2014-12-171-1/+3
|
* Adding error handling so saving node doesn't prevent us from running audit ↵tyler-ball2014-12-171-2/+14
| | | | mode - decouples converge phase and audit phase more
* Adding logic for exceptions from converge phase not interfering with audit ↵tyler-ball2014-12-171-15/+10
| | | | phase and vice-versa
* Creating our own example group class to simplify adding examples to the spec ↵tyler-ball2014-12-171-14/+42
| | | | runner
* Use windows evt log by default on windowsJay Mundrawala2014-10-221-1/+19
|
* Don't autoload windows event loggerJay Mundrawala2014-10-221-2/+0
|
* Added windows event loggingJay Mundrawala2014-10-221-0/+2
|
* Merge pull request #1924 from justanshulsharma/patch-1Serdar Sutay2014-10-101-1/+1
|\ | | | | Should use client_name instead of node_name
| * Should use client_name instead of node_nameAnshul Sharma2014-08-271-1/+1
| |
* | Remove space before paren (ruby warning)danielsdeleo2014-10-061-1/+1
| |
* | Disable unforked interval runs.Claire McQuin2014-10-011-51/+3
| | | | | | | | | | | | | | | | | | | | Clarify error message. Move fork and interval logic to application (specs pending). Clean code logic, fix specs. Allow unforked client runs with daemonize or splay
* | Improve the action and throw-label names.Chris Doherty2014-09-121-1/+1
| |
* | Re-implement immediate reboot using throw/catch, so all the end-of-runChris Doherty2014-09-101-1/+3
| | | | | | | | tasks (e.g. report handlers) still get to run.
* | Chef::Rebooter -> Chef::Platform::RebooterChris Doherty2014-09-101-2/+2
| |
* | First-pass changes for a core reboot resource. Still uses run_state instead ↵Chris Doherty2014-09-101-0/+5
| | | | | | | | of run_context.
* | Move Chef::Config path functions to Chef::Util::PathHelperJohn Keiser2014-08-301-1/+0
|/
* convert cli argument to int, tidy exception messageClaire McQuin2014-05-061-6/+1
|
* add option to abandon chef run if blocked by another for too longClaire McQuin2014-05-051-4/+8
|
* Check SSL configuration once per client run.danielsdeleo2014-03-241-4/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We want to ensure users see this. Also add a longer description of the risks of the verify_none setting and a pointer to `knife ssl check` for troubleshooting help. The warning message looks like this: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * SSL validation of HTTPS requests is disabled. HTTPS connections are still encrypted, but chef is not able to detect forged replies or man in the middle attacks. To fix this issue add an entry like this to your configuration file: ``` # Verify all HTTPS connections (recommended) ssl_verify_mode :verify_peer # OR, Verify only connections to chef-server verify_api_cert true ``` To check your SSL configuration, or troubleshoot errors, you can use the `knife ssl check` command like so: ``` knife ssl check -c /etc/chef/client.rb ``` * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ** * * * *
* use local config var in #registerLamont Granquist2014-03-241-1/+1
|
* CHEF-5134: Warn on no SSL verificationLamont Granquist2014-03-241-0/+4
| | | | | | | | | | only checking before we register the node to avoid spamming SSL verification errors on every single connection. because its in register it shouldn't warn in solo/apply use cases (you still can use remote_file in those so maybe we should also warn there? i decided that'd be more annoying than typically useful, YMMV...)
* move exception message into objectLamont Granquist2014-03-051-4/+1
|
* add ohai[:machinename]Lamont Granquist2014-03-051-1/+1
| | | | | | | | | | | | this is an ohai 7 attribute that == the output of /bin/hostname - if the FQDN exists we still prefer that, but requires correct DNS - if the machinename exists then we use that, but requires ohai 7 - then we default to the hostname which should exist on ohai 6, (but sometimes doesn't on some distros?) machinename should always be set on ohai 7, so we should entirely stop seeing CannotDetermineNodeName after it rolls out.
* Add permanent run list modification option to Chef::Clientdanielsdeleo2014-02-201-11/+15
|
* Modernize and organize Chef::Client specsdanielsdeleo2014-02-201-1/+9
|
* - Adding X-Remote-Request-Id to the set of headers for every request from ↵PrajaktaPurohit2014-02-071-0/+6
| | | | | | | | | | CCR and knife that will be sent to erchef - Each knife request has a different X-Remote-Request-Id, where as it remains the same for all requests originating from the same chef-client run. - Adding and fixing tests
* [CHEF-3506] suppress final node save when using override run listdanielsdeleo2014-02-031-5/+5
|
* Delegate sync_cookbooks to policy_builder, subclasses rely on itdanielsdeleo2014-02-031-0/+4
|
* Add public API for expanding run_list in Chef::Clientdanielsdeleo2014-01-231-0/+24
| | | | | External projects like chefspec need to do this separately so they can inject custom behavior before/after.
* Return node from Chef::Client#build_nodedanielsdeleo2014-01-231-0/+1
|
* Add indirection to allow switching policy builder implementationsdanielsdeleo2014-01-211-1/+1
|
* Extract policy building concerns from Chef::Clientdanielsdeleo2014-01-141-152/+16
| | | | | | 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.
* Add ability to run recipes directly from chef-client command lineJohn Keiser2013-12-061-0/+6
|
View Lorry Controller Status