-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
slack: Allow legacy / proxy notification use-cases #469
Comments
Relevant log output:
|
I talked to our IT folks and they said they'd be happy to move away from the proxying use-case. Question to the audience: does anyone of you use ^ this kind of custom Slack URL? |
Maybe we un-milestone the issue for now to reduce the importance somewhat? WDYT? |
I do not have a proxy to some notification system, but I don't think I am the reference here ;) I think however it would be right to warn that the slack-hook-url is not rightfully formatted, and still try it. If shoutrrr works with it, then good. If not, let's fix shoutr where/if necessary? If we are to implement our own library/behaviour/"alternative ways", then it doesn't make much sense to use an existing library for notifications ;) |
✔️ There was a warning as you can see in the log output above. It'll just be a bit hard to find out who might get surprised by this behaviour. In the case of our Dev environment, the Slack notifications just stopped happening. I'm willing to accept though that this is one of the few cases and everybody else just uses the Slack hook notation. 🤷 |
This issue was automatically considered stale due to lack of activity. Please update it and/or join our slack channels to promote it, before it automatically closes (in 7 days). |
With #368 (at least TTBOMK) we stop supporting notification use-cases like
which is what we use in our cluster(s) - it's essentially kind of a proxy for various kind of notifications.
@atighineanu was thinking we add a
--custom-slack-url
option.We should at the very least let people know in the release notes that we are changing the behaviour ... 🤷♂️
The text was updated successfully, but these errors were encountered: