potiuk commented on issue #35268: URL: https://github.com/apache/airflow/issues/35268#issuecomment-1786229157
> Who came up with the idea of giving help based on set parameters, and not all possible options? Why do you want to know who? What are you going to do with that knowledge, I wonder? BTW. In case, by any chance, you also happen to be interested WHY, (rather than who), you will find the information in the CLI https://airflow.apache.org/docs/apache-airflow/stable/cli-and-env-variables-ref.html docs - look for executors Basically Celery executor is part of "celery" provider and Celery provider "extends" CLI with new commands dynamically. Celery command is NOT airflow command, it's command contributed by Celery Executor. If you would like to discover all providers and ask them for all CLI commands they could contribute it could delay your `--help` command sometimes by up to a second. Which is bad idea. That's why decison was made that rather than finding all possible executors and all possible CLI commands, only the current executor is quickly checked to see what commands it provides. And if you have idea how to do it in the way to show possible executor commands (including upcoming executors - Amazon ones, possibly Google ones, possibly some others, and possibly commands from executors coming from providers developed outside by 3rd-parties and do it in the way that will not impact speed of CLI, PRs are most welcome. But I am not sure if you are interested in answer "why" - your "who" question was a bit strange in this context, almost as if you knew that the person was wrong without knowing or even attempting to explore "why" it has happend. It's pretty odd choice of asking questions if you ask me. -- 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]
