event stream JobDeregister event does not include purge flag

[tgross]

When a job is stopped, the event stream emits a JobDeregister event on the Job topic. But this event for whatever reason doesn't include the Purge flag that was included in the RPC request. This would be useful for post-hoc forensics, as described in #24147

[DamianArado]

Hi @tgross continuing from our earlier discussions in #24147

Will including Purge flag help us differentiate b/w jobs which are stopped and jobs which are purged?

Will this be included somewhere in the event stream's JSON?

Ex.

curl -s -v -N http://127.0.0.1:4646/v1/event/stream?topic=Job
{
  "Topic": "Job",
  "Type": "JobDeregistered",
  "Key": "<>",
  "Namespace": "default",
  "FilterKeys": null,
  "Index": 7816899,
  "Payload": {
    "Job": {
      "Stop": true,
      "Region": "global",
      "Namespace": "default",
      "ID": "<>",
      "ParentID": "",
      "Name": "<>",
      "Type": "service",
      "Priority": 50,
      "AllAtOnce": false,
      "Datacenters": [
        "dc1"
      ],
      "NodePool": "<>",
-----------
----------- more json-------
----------
      "CreateIndex": 1507847,
      "ModifyIndex": 7816899,
      "JobModifyIndex": 7816899
    }
  }
}

[tgross]

Will including Purge flag help us differentiate b/w jobs which are stopped and jobs which are purged?
Will this be included somewhere in the event stream's JSON?

Yes, that would be its purpose.