potiuk edited a comment on issue #20073: URL: https://github.com/apache/airflow/issues/20073#issuecomment-987849489
And it makes also no sense to do it, because what you essentially want to do is to provide a way to dynamically generate parameters based on the actual run being executed. Which in airflow can be done much better by imperative code rather than declarative definition. The whole idea of DAG in Airlfow is that it is imperatively generated by Python code. In this case it's the same - you should write a code that derives the parameters for scheduled run, rather than "declaratively" describe the relation between the dag run and the parameters it does. Doing it declaratively is very, very limiting and whatever you come up with there, can also be done (very easily) writing a Python code. Defining DAGs IS writing Python code. Just follow the Airflow way of doing things. -- 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]
