Events: sender_type property to differentiate between multiple event sources

[martastain]

Endpoints that accepted "x-sender" header now also accept "x-sender-type".
sender_type is stored in the database in the separate field. and it is available in the eventmodel.

@jakubjezek001 @iLLiCiTiT do you need to be able to filter by it in enroll somehow? if so, how?

[iLLiCiTiT]

All works good, but I have one note, enrolled events don't have sender type filled from headers and enroll endpoint does not allow to fill it.

[martastain]

All works good, but I have one note, enrolled events don't have sender type filled from headers and enroll endpoint does not allow to fill it.

Thanks. Good catch. I've added senderType to the request body and the enroll endpoint also supports providing sender and sender type values in headers. Both is optional, but when a value is specified both in the headers and the body, value from the body is used.

[iLLiCiTiT]

Thanks. Good catch. I've added senderType to the request body and the enroll endpoint also supports providing sender and sender type values in headers.

Nope, you didn't 🙂 , enroll still without sourceType.

[martastain]

@iLLiCiTiT i ALMOST did. it was just one git commit and git push away :) sorry