-
Notifications
You must be signed in to change notification settings - Fork 187
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 support for templating in on_failure_callback
#209
Comments
This would be a new feature, I'm going to see if it's something that's feasible. Basically, we'd need to support functionality that looks like this:
|
Hi guys, is there any eta for this release? |
@matveykortsev, there is currently a Pull Request in review with a solution to this issue. |
@jroach-astronomer I see, there is not mention in PR so haven't seen this. |
pankajastro
added a commit
that referenced
this issue
Oct 30, 2024
Add support for templating in `on_failure_callback`. Requester is specifically looking to support templated parameters that do not need to be stored in a `.py` file. Here's an example (from the issue submitted by @matveykortsev) for reference: ``` from airflow.providers.slack.notifications.slack import send_slack_notification 'on_failure_callback': [ send_slack_notification( slack_conn_id='slack', text=""" 🔴 Task Failed. *Task*: {{ ti.task_id }} *Dag*: {{ ti.dag_id }} *Execution Time*: {{ ti.execution_date }} *Log Url*: {{ ti.log_url }} """, channel="analytics-alerts", username="Airflow", ) ], ``` Closes: #209 --------- Co-authored-by: Pankaj Singh <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In reference to #206, add support for templating in
on_failure_callback
. Requester is specifically looking to support templated parameters that do not need to be stored in a.py
file.Here's an example (from the issue submitted by @matveykortsev) for reference:
@pankajastro has created an issue (#200) to ensure consistency between native Airflow and dag-factory.
The text was updated successfully, but these errors were encountered: