Expended parameters are rendered as MappedArgument #40605
Replies: 2 comments
-
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
Beta Was this translation helpful? Give feedback.
-
It can't be done this way - because you are trying to resolve the parameter at the moment when the DAG is parsed, not when the task is executed. Dynamically mapped parameters are resolved at the moment the task is about to execute - similar to all jinja templates of ours - which remain jinja templates until the task is about to be executed and they are resolved then. Converted to a discussion if more discussion is needed. |
Beta Was this translation helpful? Give feedback.
-
Apache Airflow version
Other Airflow 2 version (please specify below)
If "Other Airflow 2 version" selected, which one?
2.9.0
What happened?
When trying to expand a task group the following way:
and inside the task group trying to use company ID the following way:
The parameter is rendered the following way:
What you think should happen instead?
I would hav expected parameters to render as:
How to reproduce
create the following DAG:
Operating System
Linux
Versions of Apache Airflow Providers
No response
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions