Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move trigger dagrun to standard provider #44030

Conversation

hardeybisey
Copy link
Contributor

@hardeybisey hardeybisey commented Nov 14, 2024

Moving trigger_dagrun operator to standard provider.

airflow/operators/trigger_dagrun.py >> providers/src/airflow/providers/standard/operators/trigger_dagrun.py


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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.

hardeybisey and others added 6 commits November 14, 2024 19:38
This is mostly pointless but hey.

I didn't want to write log because there's often a log var.  I was annoyed that pre-commit was complaining about this so I just noqa'd it.  But what Kaxil wants, Kaxil gets ;)
* add clear_dag_run

* add tests

* Merge branch 'main' of https://github.com/apache/airflow into kalyan/API-84/clear_dag_run

* add ti response

* add

* use logical_date

* fix tests

* remove async

* Update airflow/api_fastapi/core_api/routes/public/dag_run.py

Co-authored-by: Pierre Jeambrun <[email protected]>

* Update airflow/api_fastapi/core_api/datamodels/dag_run.py

Co-authored-by: Pierre Jeambrun <[email protected]>

* remove type ignore

* update ti state and assert it

* reuse state

* remove breakpoint

* feedback

---------

Co-authored-by: Pierre Jeambrun <[email protected]>
The tests execution was traditionally using single "breeze testing
tests" command and you could select which test to run via TEST_TYPE.

However the recent move of providers and adding task_sdk necessitates
splitting the tests commands into separate commands for core, providers,
task_sdk, helm, integration and system.

This is done via introducing "TEST_GROUP" - which determines which
group of tests is being executed, and dedicated testing command for each
of the groups - with "db" and "non-db" variants where applicable.

Cleanup and small refactoring has been done to make it easier to
reason about parameters passed down from the command line to
docker and in-container pytest command.

Related: apache#42632
@hardeybisey hardeybisey deleted the move-trigger-dagrun-to-standard-provider branch November 15, 2024 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants