Return node object as part of chef-run execution

[tyler-ball]

Describe the Enhancement:

Customers have expressed a desire to use the state of a node as part of control flow. EG, if the node is a Windows machine perhaps they use that information to kick off a second chef-run execution.

Describe the Need:

Return the node data (the node.json that gets sent to the Chef Server) to the workstation after completing the chef-run execution.

Current Alternative

Querying this with knife. Manually looking it up on the Chef Server, EG via knife search.

Neither of these options work in a non-Chef-Server environment, thus the desire to return this information from chef-run

Questions

1. What would the UX for this look like?
2. Could we coordinate returning this information as part of Copy chef-client run output to host #135? Perhaps they end up in a shared folder, or part of a shared zip?