3rd Party Integrations

[No9]

Reading through the FAQ on providing your own uploader and came to the conclusion providing a system that implements file lock seems a little heavy handed
https://github.com/IBM/core-dump-handler/blob/main/FAQ.md#how-should-i-integrate-my-own-uploader.
For v8.0.0 I am considering adding cloud events https://github.com/cloudevents/sdk-rust
This would mean that k8s environments that have knative installed could very simply leverage those events without having to code the file lock semantics while 3rd party services can simply provide an http endpoint.

Currently considering 2 events

1. zip file created - to cater for those who want to provide their own storage location when used with useINotify=false
2. zip file uploaded - to allow people to provide their own post processors without having to rely on proprietory eventing schemes for each cloud provider or creating a polling system where that is not available.

Need to consider how failed requests are handled - exponential backoffs with a threashold to write to disk?

CC @tjungblu

[No9]

Work for this has started on this branch https://github.com/IBM/core-dump-handler/tree/cloud-event
The plan is to write the event to a json file on disk and then use that as the payload for both created and upload events.
The security scheme isn't yet confirmed - I prefer to use mTLS but that may prevent integration with publicly hosted app solutions so shared secret might also be required.
The retry requirement may also mean that the schedule option may be the only way to capture retrys so iNotify may be disabled if events are enabled.

[No9]

Initial implementation released in #122 v8.9.0 as experimental
There is container to process the file yet as this is expected to be a down stream activity but the code is in place.