justinpakzad opened a new pull request, #72746:
URL: https://github.com/apache/airflow/pull/72746
<!-- 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:
https://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.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
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
-->
---
This PR adds task state store commands to airflowctl. This would allow users
to
get, list, set, update, delete, and clear key/values in a task instance's
state
store. All of the new commands correspond to existing endpoints that are
available
via the REST API. Unit and integration tests were added for each command and
they
were also tested against an actual state store via breeze.
The commands live under the `taskinstances` group, since the state store is
scoped
to a single task instance (`dag_id` + `run_id` + `task_id` + `map_index`):
- `list-state-store` - list all state store entries for a task instance
- `get-state-store` - retrieve a single entry by key
- `set-state-store` - create or overwrite a key (PUT)
- `update-state-store` - update the value of an existing key (PATCH)
- `delete-state-store` - delete a single key
- `clear-state-store` - delete all keys for a task instance
All commands accept `--map-index` to address a specific mapped task
instance, and
`clear-state-store` additionally accepts `--all-map-indices` to clear across
every
map index.
Follow-up to #70771
##### 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".
-->
- [x] Yes (Claude Opus 4.8)
<!--
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]
