Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Report client run mode to data collector #9218
Describe the Enhancement:
With the current client run reports we are unable to determine if a client run was run under the effortless pattern, in target mode, or other modes. It would be better if we had a top level field that reported the circumstances of the run (target mode, effortless, local mode, chef-server?, others?).
Describe the Need:
We can display this information in automate, and users can have a better idea of the types of nodes they are running.
We use the chef_server_fqdn to determine if it was run as localmode, as this should be localhost if so. We have no other information to go on.
Can We Help You Implement This?:
how strict is the ingestion of the JSON on the server-side? i've been wary of adding any top-level keys to the data collector output for fear of breaking it (and creating a backwards incompatibility issue).
I think we could reuse the top level "source" field in the current payload. From the original RFC it is an enum of chef_client and chef_solo, and we don't have validation on the values received in automate.