Skip to content

Conversation

@uranusjr
Copy link
Member

@uranusjr uranusjr commented Sep 2, 2021

Close #17931.

The user will need to put custom timetables in a plugin and do

class MyPlugin(AirflowPlugin):
    timetables = [MyTimetable]

One question since I need to incorporate this into the documentation (#17552). Where should I put the example plugin code? Since timetable requires registration, the user can’t declare a timetable in a DAG file anymore; #17552 is currently putting the timetable code in example_dags.

Copy link
Member

@ashb ashb left a comment

Choose a reason for hiding this comment

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

Code/approach looks good

@github-actions github-actions bot added the full tests needed We need to run full set of tests for this PR to merge label Sep 3, 2021
@github-actions
Copy link

github-actions bot commented Sep 3, 2021

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

@uranusjr uranusjr force-pushed the aip-39-timetable-registration branch from 11fd7a2 to 568a6b8 Compare September 3, 2021 09:31
@uranusjr uranusjr merged commit be7efb1 into apache:main Sep 3, 2021
@uranusjr uranusjr deleted the aip-39-timetable-registration branch September 3, 2021 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:plugins area:serialization full tests needed We need to run full set of tests for this PR to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Timetable registration a la OperatorLinks

2 participants