-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Add Amazon SNS Notifier #33828
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
Add Amazon SNS Notifier #33828
Conversation
| ) | ||
|
|
||
|
|
||
| send_sns_notification = SnsNotifier |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is it needed? Could not we just call directly SnsNotifier?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same convention in other notifiers ¯\_(ツ)_/¯.
| send_chime_notification = ChimeNotifier |
| send_slack_notification = SlackNotifier |
| send_apprise_notification = AppriseNotifier |
And this conventions was here since first notifier implemented, I know because this PR sits in my local machine for a long time I've just waited until 2.6 released... and have a time to push it only now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not against it but I dont feel it is necessary and bring more complexity by adding a proxy name ¯_(ツ)_/¯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tried to find why initially we decide to use snake_case for notifiers, but with no luck
Co-authored-by: Vincent <97131062+vincbeck@users.noreply.github.com>
Implements
SnsNotifieras part of Amazon Provider^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.