jedcunningham commented on PR #59430: URL: https://github.com/apache/airflow/pull/59430#issuecomment-3677982090
I think you may be mixing up the 2 different versions we have now. Bundle versioning: The deployment manager can choose to use a versioned dag bundle (and likewise the dag author can also use `disable_bundle_versioning`) to control whether versioned dag code is used when running a task. This can be controlled. But it only controls code used to execute tasks. Dag versioning: a.k.a keep history of serdags used in runs. This is always on - there is no mechanism to disable it. This is what the static check here is covering. This powers the UI to show what the dag looked like historically. > something that we've been also doing in Airflow 2 and it never created huge issue (except a bit more often DB update for those ? Depends on perspective I guess. I'd argue that tasks disappearing from the UI when dag structure changes is pretty bad. But either way, there is currently no way to control that, and that was by design. -- 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]
