bugraoz93 opened a new pull request, #45300:
URL: https://github.com/apache/airflow/pull/45300

   **Summary**
   This PR introduces a central API communication mechanism for the CLI and 
adopts one of the broadest endpoint ranges in the API, focusing on connection 
commands. After several iterations to automate API call generation and handle 
edge cases, I couldn't achieve a fully dynamic request generation process. 
Instead, I landed on a structure similar to TaskSDK <-> ExecutionAPI. This 
approach simplifies reviews, maintains consistency across clients, and opens 
the door for better automation in future iterations, possibly in 3.1 or 3.2.
   
   **Implementation Details**
   
   - Added a central API communication mechanism for the CLI.
   - Integrated connection_command.py with unit tests.
   - Implemented most of the necessary CLI operations.
   - Data model generation from RestAPI to CLI is handled using uv.
   - Added decorators to cascade generic processes to operations.
   - Created a testing framework for CLI testing, with an example 
implementation for connection command.
   - Pending Work
   - Some minor features related to the connection command are still in 
progress and will be added in follow-up updates before 3.0.
   
   **Notes on task_command**
   While working on this, I realized that task_command behaves more like a 
local_command than a remote_command. This needs further discussion, especially 
regarding its integration with TaskSDK. From the CLI perspective, depending on 
TaskSDK seems cleaner than directly calling ExecutionAPI, as it avoids 
duplication and keeps the structure consistent. Even if the CLI calls TaskSDK, 
the two-hop process to reach the ExecutionAPI feels a bit redundant. What do 
you think, @ashb?
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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]

Reply via email to