Skip to content

Add ability to quickly trigger a DAG #15591

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

Merged
merged 1 commit into from
Apr 29, 2021

Conversation

bbovenzi
Copy link
Contributor

@bbovenzi bbovenzi commented Apr 29, 2021

From talking with some Airflow users, most of the time people don't need to edit the config when manually triggering a DAG.

To save users from an unnecessary step, I turned the Trigger DAG button to a dropdown that allows you to do an immediate trigger and a second option that will still direct you to the trigger DAG page to edit conf.

Screen Shot 2021-04-28 at 2 07 32 PM

Apr-29-2021 11-06-11


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

@boring-cyborg boring-cyborg bot added area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues labels Apr 29, 2021
Copy link
Member

@kaxil kaxil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<3 Thanks I know some of the users have asked for this on Slack too

@kaxil kaxil added this to the Airflow 2.1 milestone Apr 29, 2021
Copy link
Contributor

@ryanahamilton ryanahamilton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love this UX enhancement!

@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 Apr 29, 2021
@github-actions
Copy link

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 master or amend the last commit of the PR, and push it with --force-with-lease.

@ryanahamilton ryanahamilton merged commit 943e3ca into apache:master Apr 29, 2021
@ryanahamilton ryanahamilton deleted the quick-trigger-dag branch April 29, 2021 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues 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.

4 participants