Skip to content
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

Open
dholbach opened this issue Nov 30, 2021 · 6 comments
Open

slack: Allow legacy / proxy notification use-cases #469

dholbach opened this issue Nov 30, 2021 · 6 comments
Labels
keep This won't be closed by the stale bot. notifications

Comments

@dholbach
Copy link
Member

With #368 (at least TTBOMK) we stop supporting notification use-cases like

--slack-hook-url=http://eventmanager.notification.svc.cluster.local./api/notification/slack/2/kured

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 ... 🤷‍♂️

@dholbach dholbach added this to the 1.8.2 milestone Nov 30, 2021
@dholbach
Copy link
Member Author

Relevant log output:

2021-11-29T15:57:52.684347460Z time="2021-11-29T15:57:52Z" level=warning msg="Deprecated flag(s). Please use --notify-url flag instead."
2021-11-29T15:57:52.684404989Z time="2021-11-29T15:57:52Z" level=warning msg="slack-hook-url is not properly formatted...no notification will be sent: <nil>\n"

@dholbach
Copy link
Member Author

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?

@dholbach
Copy link
Member Author

Maybe we un-milestone the issue for now to reduce the importance somewhat? WDYT?

@evrardjp
Copy link
Collaborator

evrardjp commented Dec 1, 2021

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 ;)

@dholbach
Copy link
Member Author

dholbach commented Dec 1, 2021

✔️ 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. 🤷

@dholbach dholbach removed this from the 1.8.2 milestone Dec 1, 2021
@github-actions
Copy link

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).

@dholbach dholbach added keep This won't be closed by the stale bot. and removed no-issue-activity labels Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keep This won't be closed by the stale bot. notifications
Projects
None yet
Development

No branches or pull requests

2 participants