@laurynmm Could you please review this one?

@Niloth-p - Thanks for working on this update! The changes look fine to me, so mentioning@timabbott for an integration review.

Noting that the updates here to use "topic" instead of "subject" in the send message dict does make this inconsistent with the other documented examples forsend_message in this repository. That API change to the messages endpoint dates back to Zulip 2.0, so it does feel like it should be fine to update at this point.

These updates are related to the documentation updates inzulip/zulip#32780.

Reviewed, ping me on chat.zulip.org when the remaining thing is resolved.

Oops, thank you!

There was no error handling previously, errors were silently ignored.
Added some basic logging now. Log to both a log file, as well as the stderr, in case they have a better system for server stderr, whereas errors logged to the log file could be easily missed.
(Normal printing to terminal does not work in the post-receive hook.)

From the API documentation forsend-message, the error messages are updated to use "channel" and not "stream". Though the codes haven't been updated.
I verified it by setting up the integration anyways. Because I wasn't familiar with thepost-receive hook's behavior.

I have now verified that the error only returns{'result': 'error', 'msg': 'Missing channel', 'code': 'BAD_REQUEST'} when there's no channel value being set. So, there's no mention of a "stream", and is hence safe.

Also, I can understand if we'd want to do this renaming "stream", "subject" occurrences in all integration config files, commandline arguments and other user-facing parts, in a single pass, instead of one integration at a time. Let me know. This minimalist approach was based off of my experience with the integration docs.