Conceptually, a resource is supposed to be a set of properties that describe what you want some part of the system to be, like a `package` named `apache2` at version `2.6.25`, but in practice many resources have a lot of attributes that describe *how* you change the system's state, like `init_command` for the service resource or the `backup` attribute on the file resource. For reporting, our goal is to track changes to system state so we want to focus on the *what* and not the *how*. So, `state_attrs` are the things that describe the `what`.

As it relates to reporting, the relevant code is here: https://github.com/opscode/chef/blob/master/lib/chef/resource_reporter.rb#L55 and here: https://github.com/opscode/chef/blob/master/lib/chef/resource_reporter.rb#L83-87

Not sure how best to handle that for this case.