diff options
| author | Tim Smith <tsmith@chef.io> | 2019-03-11 12:16:51 -0700 |
|---|---|---|
| committer | Tim Smith <tsmith@chef.io> | 2019-03-11 12:16:51 -0700 |
| commit | b870d8c578a6424e405ec2083d5f47d331f09d14 (patch) | |
| tree | b3c6ec7a073ecfe2bdfdd7bb7dbde5356cfb0f2f | |
| parent | a2ac8bc237a84a00d3a44f3a18c26140a8c35b3e (diff) | |
| download | chef-b870d8c578a6424e405ec2083d5f47d331f09d14.tar.gz | |
Remove extra spaces from the dev doc
Signed-off-by: Tim Smith <tsmith@chef.io>
| -rw-r--r-- | docs/dev/data_collector.md | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/docs/dev/data_collector.md b/docs/dev/data_collector.md index 168bf206e2..be0a92e7fb 100644 --- a/docs/dev/data_collector.md +++ b/docs/dev/data_collector.md @@ -85,7 +85,7 @@ ConfigValidation should probably be merged into one renamed Config module to iso These are separated out into their own modules, which are very deliberately not mixed into the main Data Collector. They use the Data Collector and Action Collection public interfaces. They are stateless themselves. This keeps the collaboration between them and the Data Collector very easy to understand. The start message is -relatively simple and straightforwards. The complication of the end message is mostly due to walking through the Action Collection and all the collected action +relatively simple and straightforwards. The complication of the end message is mostly due to walking through the Action Collection and all the collected action records from the entire run, along with a lot of defensive programming to deal with early errors. ## Relevant Event Sequence @@ -112,6 +112,3 @@ As it happens in the actual chef-client run: 13. `run_status.stop_clock` 14. `run_status.exception = exception` if it failed 15. `events.run_completed(node, run_status)` or `events.run_failed(exception, run_status)` - - - |