The GitHub Actions job "Tests (AMD)" on airflow.git/backport-f7dec02-v3-3-test 
has succeeded.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
fdf62c86f987249d18689fad74b27d2f2f7d52d0 / Jarek Potiuk <[email protected]>
[v3-3-test] Restore pluggable email backend for task failure and retry alerts 
(#69877)

Since #57354, task email_on_failure / email_on_retry alerts were routed
unconditionally through SmtpNotifier, silently ignoring the
[email] email_backend configuration. Custom backends (SES, SendGrid,
org-internal) stopped delivering failure/retry emails even though the
deprecated email_on_* parameters still worked.

This restores the old behaviour using the existing [email] email_backend
option -- no new configuration is introduced:

- A non-default [email] email_backend is transparently wrapped in a new
  LegacyEmailBackendNotifier, so existing SES / SendGrid / custom backends
  keep delivering alerts unchanged. The backend is resolved from config at
  notify time, so the Task SDK keeps no static dependency on
  airflow.utils.email.
- Otherwise the default SmtpNotifier is used, exactly as before.

The notifier lives in the Task SDK (airflow.sdk.execution_time.email_backend)
next to its only caller, so no extra provider needs to be installed for a
custom email backend to keep working.

Both failure-email entry points (the worker task-runner path and the
DAG-processor callback path) funnel through the same function, so the
selected backend is used consistently regardless of how the task failed.

The deprecated email_on_* parameters are not un-deprecated; this only keeps
their existing behaviour pluggable until removal in Airflow 4.
(cherry picked from commit f7dec02b2a9d88e886d0d3b2fd1919edbf2ff8af)

Co-authored-by: Jarek Potiuk <[email protected]>

Report URL: https://github.com/apache/airflow/actions/runs/29756139722

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to