You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
airflow upgrade_check should check python_callable is not used in TriggerDagRunOperator.
As of #6317, python_callable is no longer supported (in any 2.x version) and dag tasks using it will fail to parse.
This is not currently verified by upgrade_check and I caught it only after upgrading to 2.x.
What you expected to happen
upgrade_check to verify parameters of TriggerDagRunOperator and warn that upgrade_check should be removed and replaced with passing conf dictionary directly.
How to reproduce
run airflow upgrade_check on a dag with the following task (from PR):
There are no further releases of upgrade check tool as 1.10 is EOL.
In any case this is not something that can be added to the upgrade check as the conf param doesn't exist in TriggerDagRunOperator of 1.10 - It wasn't backported so this specific change is a breaking change. The upgrade checker will not suggest changes that results in broken dags on 1.10
Apache Airflow version
2.1.2
Operating System
Red Hat Enterprise Linux Server 7.6 (Maipo)
Versions of Apache Airflow Providers
No response
Deployment
Virtualenv installation
Deployment details
No response
What happened
airflow upgrade_check
should checkpython_callable
is not used inTriggerDagRunOperator
.As of #6317,
python_callable
is no longer supported (in any 2.x version) and dag tasks using it will fail to parse.This is not currently verified by upgrade_check and I caught it only after upgrading to 2.x.
What you expected to happen
upgrade_check to verify parameters of
TriggerDagRunOperator
and warn thatupgrade_check
should be removed and replaced with passingconf
dictionary directly.How to reproduce
run
airflow upgrade_check
on a dag with the following task (from PR):Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: