-
Notifications
You must be signed in to change notification settings - Fork 19
Add Dag Paused and Latest Dag Runs endpoint #2
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
Open
benjamingregory
wants to merge
1
commit into
master
Choose a base branch
from
feature/pause_endpoint
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking about it, we may want to change the route to be '/dags/string:dag_id', have the call expect a POST'ed JSON object that currently only expect { "paused": true/false }, and then change the method from POST to PATCH. That way we can extend this later for any other update operations on a DAG. Maybe change the function def name to be "update_dag".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about a
POSTto/dagswith all the params in the object, passing in the following?{ "dag_id":"dag1", "paused": true/false }Then you could bulk update in one request:
{ "dag_id":"dag1,dag2,dag3", "paused": true/false }There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in general for the case of multiple records being updated in the same call we can add a secondary URL. ie, have both /dags and /dags/[dag_id]. However looking at the schema, since pretty much the only property of a dag that should be manually changed is the "is_paused" property, this should be fine. However let's make the JSON be:
{ "dag_id": ["dag1","dag2","dag3"], "paused": true/false }, and make it aPUT. Try to keep things RESTful, reservePOSTfor just creation of records.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cwurtz Got it.
A thought though: Should you be able to update multiple records with varying values? So set
dag1anddag2totruebutdag3tofalse?In that case, the above wouldn't work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you think there is a use case for it. I'd imagine the vast majority of the time if someone is updating multiple dags, it would be to set them all as true or all as false. Worst case they have to make two API calls.
If you disagree and think it would be more common, we could do something like:
And optionally allow just
{ "dag_id": "dag1", "paused": false }for updating a single dag (check the input at the start of the call and coerce it into an array to keep the logic consistent)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that might be a bit much for now. I'll update the PR to include
PUTcalls and to accept multiple dag_ids but that's where I'll leave it.