amarlearning commented on issue #46506: URL: https://github.com/apache/airflow/issues/46506#issuecomment-2762705585
Hi @uranusjr, As I'm relatively new to the Airflow community, I've been diving deep into the codebase to understand it better. After carefully studying how the `airflow tasks run` command works in Airflow 3.0, I noticed it's part of a transition toward the Task SDK approach. While still used internally by some executors, it's no longer in the user-facing CLI. I'm a bit concerned that changing the command syntax might introduce a breaking change during this transitional period, potentially affecting internal executor implementations. I've also noticed comments like `TODO: TaskSDK: Compat, remove when KubeExecutor is fully moved over to TaskSDK` which suggest this command pattern is temporary. As someone eager to contribute meaningfully, I'm wondering if focusing on helping with the Task SDK transition might be more valuable for the project long term. I'd appreciate your guidance on whether this syntax change is still a priority given the architectural direction. I'm happy to proceed with the original issue or redirect my efforts based on what would best serve the project. -- 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]
