[ZBXNEXT-6482] Signal webhook Created: 2021 Feb 01 Updated: 2024 Apr 10 |
|
Status: | Reopened |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Templates (T) |
Affects Version/s: | None |
Fix Version/s: | 5.0.9rc1, 5.2.5rc1, 5.4.0alpha2 |
Type: | New Feature Request | Priority: | Trivial |
Reporter: | Aleksandrs Larionovs (Inactive) | Assignee: | Zabbix Support Team |
Resolution: | Unresolved | Votes: | 5 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() |
Team: |
Description |
Create webhook for Signal messenger. |
Comments |
Comment by Nathan Liefting [ 2021 Mar 30 ] |
Looks like this has been added to the roadmap now anyway?
|
Comment by Marco Hofmann [ 2021 Apr 26 ] |
I don't understand the status of this request. It's "Declined", "Closed", has "fixed Versions", stands on the "roadmap" and ist not in the GIT repo. So is it now?
|
Comment by richlv [ 2021 May 20 ] |
Schroedinger's issue? Marco has a point, though. Something's obviously wrong with this issue. |
Comment by Aleksandrs Larionovs (Inactive) [ 2021 May 21 ] |
|
Comment by Edgar Akhmetshin [ 2022 Jun 29 ] |
Why declined? |
Comment by dimir [ 2024 Feb 12 ] |
Looks like back then there was some functionality in Zabbix missing, like encryption mechanisms. Could be now it's not the case anymore. Will see if I can get it some attention. |
Comment by Vjaceslavs Bogdanovs [ 2024 Feb 23 ] |
The typical flow here would be to implement the required crypto functions (AES-GCM-SIV, etc) for the Zabbix JS engine and then this ticket could be implemented by the integration team. Currently, this ticket is still being blocked. |