delta/ruby-gems/chef.git/spec/unit/data_collector, branch https_shell github.com: opscode/chef.git Add deprecations to Data Collector competion message 2016-10-29T04:13:36+00:00 Adam Leff adam@leff.co 2016-10-28T22:43:34+00:00 3a4442b96ba2005a9616e0f3137f651580a06ee7 By adding deprecation warnings to Data Collector, receivers of Data Collector messages can easily identify nodes that would need attention to their versions/cookbooks before a major version Chef upgrade would be successful. Signed-off-by: Adam Leff <adam@leff.co> 
By adding deprecation warnings to Data Collector, receivers of
Data Collector messages can easily identify nodes that would need
attention to their versions/cookbooks before a major version Chef
upgrade would be successful.

Signed-off-by: Adam Leff <adam@leff.co>
fix Style/BlockDelimiters, Style/MultilineBlockLayout and 0.42.0 engine upgrade 2016-08-17T20:25:02+00:00 Lamont Granquist lamont@scriptkiddie.org 2016-08-17T19:15:26+00:00 a0c32511bc6634538374ca4b433032b8acd05f96 Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org> 
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
ensuring the node in the run_converge message is a node object and that it gets serialized correctly 2016-06-28T21:19:54+00:00 Adam Leff adam@leff.co 2016-06-28T21:02:37+00:00 5137634af0777d8a49b0347b08eddd6aae0ecec7 






Adding node object to run_converge message, include ignore_failure property
2016-06-28T20:02:41+00:00

Adam Leff
adam@leff.co

2016-06-28T15:24:23+00:00

3f6db5dc96b5ecb552a491e77730356e8df2021d

Many use cases that involve consuming the run_converge messages and
displaying them to end users include needing additional data about
the node that generated the run_converge message. This change
consolidates the run_converge and node_update message into a single
message making it easier for users to filter run_converge messages
based on attributes and criteria of the node itself.

Additionally, the ignore_failure property on a resource is now
included for each resource in the resource list so end users can
decided whether the failure was a hard failure or a soft failure.





Many use cases that involve consuming the run_converge messages and
displaying them to end users include needing additional data about
the node that generated the run_converge message. This change
consolidates the run_converge and node_update message into a single
message making it easier for users to filter run_converge messages
based on attributes and criteria of the node itself.

Additionally, the ignore_failure property on a resource is now
included for each resource in the resource list so end users can
decided whether the failure was a hard failure or a soft failure.







Expand data_collector resource list to include all resources
2016-06-24T18:48:42+00:00

Adam Leff
adam@leff.co

2016-06-23T03:14:55+00:00

bb56a100caf7de9b7f0bbcb1377ba7f7cae05f90

Historically when a Chef run fails, the event handlers only report
on resources that have been processed during the run. This change
allows the Data Collector to report those resources in the resource
collection that have not yet been processed so users can better
ascertain how much of their run was completed, and specifically
what resources were not processed as a result of the Chef failure.

Instead of building up a list of resources as they are processed,
this change instead creates a resource report for each resource+action
in the resource collection and then modifies each of those reports
once the resource is processed.





Historically when a Chef run fails, the event handlers only report
on resources that have been processed during the run. This change
allows the Data Collector to report those resources in the resource
collection that have not yet been processed so users can better
ascertain how much of their run was completed, and specifically
what resources were not processed as a result of the Chef failure.

Instead of building up a list of resources as they are processed,
this change instead creates a resource report for each resource+action
in the resource collection and then modifies each of those reports
once the resource is processed.







bug fix: correctly write out data collector metadata file
2016-06-10T16:11:46+00:00

Adam Leff
adam@leff.co

2016-06-10T16:11:40+00:00

54ced0da2bd835e3753cbe51e588cf3e8040a6c9

When we changed the messages from class instances to a module, the
reading of metadata into an instance variable was removed and
introduced a bug when updating metadata. This bug causes the
metadata to be properly read from disk, updated, but then the
metadata from disk is simply re-written to disk without the
intended updates.





When we changed the messages from class instances to a module, the
reading of metadata into an instance variable was removed and
introduced a bug when updating metadata. This bug causes the
metadata to be properly read from disk, updated, but then the
metadata from disk is simply re-written to disk without the
intended updates.







Bug fix: updated_resource_count should only include updated resources
2016-06-07T19:39:06+00:00

Adam Leff
adam@leff.co

2016-06-07T19:39:06+00:00

c4cf0bbf1836fb70b0dc3aaf2f5df0399f5633ee

After adding up-to-date and skipped resources to the DataCollector
resource list, the logic that computed the number of resources
updated needed to change accordingly. This change fixes that
bug and also eliminates an unnecessary counter that tracks
the total number of resources.





After adding up-to-date and skipped resources to the DataCollector
resource list, the logic that computed the number of resources
updated needed to change accordingly. This change fixes that
bug and also eliminates an unnecessary counter that tracks
the total number of resources.







Creation of the new DataCollector reporter
2016-06-02T19:09:59+00:00

Adam Leff
adam@leff.co

2016-05-18T18:32:33+00:00

e3039ee388b5a5f9dd6a90f74adc9a4bcf1eec8a

The DataCollector reporter is a new method for exporting data about your
Chef run. The details of this new feature can be found in
[RFC 077](https://github.com/chef/chef-rfc/blob/master/rfc077-mode-agnostic-data-collection.md).

Using the existing `EventDispatch` mechanics, the DataCollector reporter
collects data about a Chef run (when it starts, when it ends, what
resources were modified, etc.) and then POSTs them to a Data Collector
server URL that can be specified in your Chef configuration.

While similar functionality exists using the `ResourceReporter` and Chef
Reporting, a new implementation was done to decouple the reporting of this
data from requiring the use of a Chef Server (in the case of Chef Reporting),
opening the door to users being able to implement their own webhook-style
receiver to receive these messages and analyze them accordingly.





The DataCollector reporter is a new method for exporting data about your
Chef run. The details of this new feature can be found in
[RFC 077](https://github.com/chef/chef-rfc/blob/master/rfc077-mode-agnostic-data-collection.md).

Using the existing `EventDispatch` mechanics, the DataCollector reporter
collects data about a Chef run (when it starts, when it ends, what
resources were modified, etc.) and then POSTs them to a Data Collector
server URL that can be specified in your Chef configuration.

While similar functionality exists using the `ResourceReporter` and Chef
Reporting, a new implementation was done to decouple the reporting of this
data from requiring the use of a Chef Server (in the case of Chef Reporting),
opening the door to users being able to implement their own webhook-style
receiver to receive these messages and analyze them accordingly.