darkag commented on issue #65012: URL: https://github.com/apache/airflow/issues/65012#issuecomment-4333813292
> So with [hardcoded](https://github.com/apache/airflow/blame/b22d7516e07d62d27dbdf12f910ba141fc06a370/task-sdk/src/airflow/sdk/execution_time/task_runner.py#L1578) `SmptNotifier`, if one wants to stick with another notification backend (we use AWS SES), it forces them to update all DAGs with specific `on_*_callback` argument? Yes, in a way since email_on** options are deprecated, we'll have to do it anyway, but with hardcoded smtpNotifier you don't have a grace period to do it. In a more global perspective having a way to use a "common mail notifier" that can determine the notifier from connection (like what is done with the common sql provider) would be clearly better in case of email backend change -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
