kevinhongzl opened a new pull request, #67356:
URL: https://github.com/apache/airflow/pull/67356
<!-- 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
-->
## Summary
Task parameters were immutable when debugging dynamic task mappings using
the CLI `airflow tasks test`. This meant we couldn't override parameters on the
fly, nor could we easily test mapped tasks that relied on upstream XCom
arguments. This PR updates the Airflow CLI to support local testing of
dynamically mapped tasks.
closes: #56953
## Params Overrides Behavior
The tables below outline how our updated `airflow tasks test` handles
combinations of expansion types, argument sources, and the presence of CLI task
parameter overrides.
#### 1. Positional Arguments from `expand()`
| Argument Type | With CLI Task Params | Without CLI Task Params |
| :--- | :--- | :--- |
| **Literal Values** | Overrides the original task parameters with the
single provided parameter value. | Runs tests using the original values defined
for that specific map index in the DAG. |
| **XCom Arguments** | Uses the user-provided input value to successfully
execute and test the task. | Fails immediately with the expected `XCom not
found` exception. |
#### 2. Keyword Arguments from `expand_kwargs()`
| Argument Type | With CLI Task Params | Without CLI Task Params |
| :--- | :--- | :--- |
| **Literal Values** | Updates the mapped keyword arguments for that index
with the new CLI task parameters. | Runs tests using the baseline keyword
arguments defined for that map index in the DAG. |
| **XCom Arguments** | Uses the user-provided input dictionary to
successfully execute and test the task. | Fails immediately with the expected
`XCom not found` exception. |
---
##### 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: [] 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]
