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

Allow filtering DAGS by tags in the REST API #18090

Merged
merged 1 commit into from
Sep 8, 2021

Conversation

ephraimbuddy
Copy link
Contributor

This PR adds a change to allow filtering DAGs by tags


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.

This PR adds a change to allow filtering DAGs by tags
@boring-cyborg boring-cyborg bot added the area:API Airflow's REST/HTTP API label Sep 8, 2021
@github-actions
Copy link

github-actions bot commented Sep 8, 2021

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

@github-actions github-actions bot added the okay to merge It's ok to merge this PR as it does not require more tests label Sep 8, 2021
@ephraimbuddy ephraimbuddy added this to the Airflow 2.2 milestone Sep 8, 2021
@ephraimbuddy ephraimbuddy merged commit ff64fe8 into apache:main Sep 8, 2021
@ephraimbuddy ephraimbuddy deleted the filter-by-tags branch September 8, 2021 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:API Airflow's REST/HTTP API okay to merge It's ok to merge this PR as it does not require more tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants