-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
Add fields to dagrun endpoint #23440
Conversation
* data_interval_start * data_interval_end * last_scheduling_decision * run_type
@@ -1046,6 +1094,10 @@ def test_should_response_200_for_matching_execution_date_logical_date(self): | |||
"external_trigger": True, | |||
"start_date": None, | |||
"state": "queued", | |||
"data_interval_end": "2020-11-10T08:25:56.939143+00:00", | |||
"data_interval_start": "2020-11-10T08:25:56.939143+00:00", |
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.
Should we use this opportunity to refactor these hardcoded dates? We could have logical_date
and execution_date
as constants and pass them instead of these dates?
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.
Thanks @ephraimbuddy, made this one and another test to use constants.
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. |
Add below fields to dagrun endpoint :
closes: #23415
related: #23415