jscheffl commented on issue #39904: URL: https://github.com/apache/airflow/issues/39904#issuecomment-2137359292
Yes, there was a bit of discussion in the community about changing the (previous, you could rate it "legacy") `conf` that is merged with the later introduced "params" but no decision was made. It might be something that could be made cleaner in an Airflow 3 I assume. @hussein-awala made an attempt in a PR (see https://github.com/apache/airflow/pull/29174) to clean this up... but somehow it never made it. In general persisting the params at point of start sounds reasonable but might be treated as a breaking change, I assume a lot of users on the contrary rely on an option to dynamically evaluate. If this behavior is to be changed, at least there would be an option needed to change to previous logic for backwards compatibility. I'll put the request as a discussion item into a future Airflow 3.0 list. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
