bugraoz93 commented on issue #45661: URL: https://github.com/apache/airflow/issues/45661#issuecomment-2745351211
Hey @jason810496 @jx2lee @josix @Prab-27, I still need to finalise a couple of CI and breeze steps for checking the unit test properly for capture problems and easier-to-ship code via local dev tools via `breeze` #48099. There are a few limitations at the moment, but I will spend time and finish that work. Then we can start creating PRs in airflow-ctl. Auto generation update, I did a couple of trials. For now, what most makes sense is to autogenerate via mapping (1-1) the command-operation relation within the commands. I mean let's say we have `jobs operation` (under [airflow-ctl/src/airflowctl/api/operations.py](https://github.com/apache/airflow/blob/main/airflow-ctl/src/airflowctl/api/operations.py)) and `list` method, this means the autogeneration part will generate `airflowctl jobs list` with proper parameters (mandatory or not) and return the results in a standard output format. From this point (automation implementation is not blocking anymore but CI works still is), we should focus on the features we cannot provide with this 1-1 mapping, for example, we have bulk operations where they need to be utilised for file operations we are providing under [airflow-core/src/airflow/cli/commands](https://github.com/apache/airflow/tree/main/airflow-core/src/airflow/cli/commands). We should implement those behaviours with API calls. There are still a few elements we can not mimic via `Public API` such as the `airflow dags test`, we should skip these transitions under `airflowctl`. Thanks for participating in making this happen! We will be unblocked in 1-2 days and I will ping you from this umbrella issue. -- 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]
