eladkal commented on issue #33916: URL: https://github.com/apache/airflow/issues/33916#issuecomment-1699598249
I don't see how this issue contradict that. The goal here is to make Executor be the same as Notifiers: https://airflow.apache.org/docs/apache-airflow-providers/core-extensions/notifications.html We have information about it in core and for the detailed info we refer to providers. The concept where code sits in one package yet documentation in another one is wrong to my taste. 1. It creates confusion. 2. When code is updated documentation will not follow. I don't think that things like how to configure Celery queue or info about git-sync of dag files to K8s workers should stay in airflow core docs. What is the motivation for this? Airflow core should have high level details - possibly a compare of capabilities between executors - anything that is higher level than a specific executor. If you still believe that this contradict the accepted vote I'd be happy to start a new discussion. -- 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]
