Suraj-kumar00 opened a new pull request, #63889:
URL: https://github.com/apache/airflow/pull/63889

   Adds Task Instance management support to the airflowctl CLI, enabling users 
to get, list, clear, and update task instances directly from the terminal.
   
   closes: #61547
   
   ### Changes
   
   **airflow-ctl/src/airflowctl/api/operations.py**
   - Added 
[TaskInstanceOperations](cci:2://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:896:0-948:19)
 class with 
[get](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:371:4-377:19),
 
[list](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:605:4-639:9),
 
[clear](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:919:4-930:19),
 and 
[update](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:481:4-492:19)
 methods.
   - Uses existing auto-generated Pydantic models for request/response 
validation.
   - Intelligently unwraps Airflow's nested 
[TaskInstanceCollectionResponse](cci:2://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/datamodels/generated.py:2021:0-2027:63)
 wrappers natively for endpoints returning 
[get](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:371:4-377:19)
 and 
[update](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:481:4-492:19)
 operations to prevent Pydantic validation crashes.
   
   **airflow-ctl/src/airflowctl/api/client.py**
   - Added `task_instances` property to `Client`, enabling the auto-generated 
CLI commands to wire up successfully.
   
   **airflow-ctl/src/airflowctl/ctl/cli_config.py**
   - Added `"clear"` to `output_command_list` for proper CLI output rendering.
   - Enhanced API field parser to automatically convert comma-separated string 
CLI arguments into properly formatted arrays/lists when the target Pydantic API 
model expects a list (e.g. `['task_1', 'task_2']` for `--task-id`).
   
   **airflow-ctl/tests/airflow_ctl/api/test_operations.py**
   - Added comprehensive 
[TestTaskInstanceOperations](cci:2://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/tests/airflow_ctl/api/test_operations.py:1711:0-1871:54)
 test suite with 6 focused unit tests.
   - Covers 
[get](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:371:4-377:19),
 
[list](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:605:4-639:9),
 
[clear](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:919:4-930:19)
 (default and with options), and 
[update](cci:1://file:///Users/suraj/Documents/Personal-work/airflow/airflow-ctl/src/airflowctl/api/operations.py:481:4-492:19)
 (state change and note addition).
   - Follows the existing XCom test pattern from #61021.
   
   **airflow-ctl-tests/tests/airflowctl_tests/test_airflowctl_commands.py**
   - Added end-to-end integration tests mapping all 4 `taskinstance` commands 
to their expected execution hashes.
   
   ### New CLI Commands
   
   ```bash
   airflowctl taskinstance list --dag-id <dag_id> --dag-run-id <run_id>
   airflowctl taskinstance get --dag-id <dag_id> --dag-run-id <run_id> 
--task-id <task_id>
   airflowctl taskinstance clear --dag-id <dag_id> [--dry-run] [--only-failed] 
[--task-ids ...]
   airflowctl taskinstance update --dag-id <dag_id> --dag-run-id <run_id> 
--task-id <task_id> [--new-state <state>] [--note <note>]
   ```
   
   <img width="582" height="371" alt="Screenshot 2026-03-18 at 9 32 30 PM" 
src="https://github.com/user-attachments/assets/c8d8e3a4-648d-4b31-ad44-869f9fafca3a";
 />
   
   
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   
   
   


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