Hi @r39132 , I have refined the implementation for this `next_execution` CLI.
**Implementation**
- It can handle different schedule_interval (Cron, timedelta, `None`, preset
including "@once")
- For `None` or `@once` schedule_interval, it will return `None` as result
- If there is no `latest_execution_date` found, it prints a reminder ("Only
applicable when there is execution record found") and returns `None` as result.
- It will print a reminder if the DAG is paused at that moment.
**Tests**
Test cases has been added based on four example DAG files
- 'example_bash_operator' (schedule_interval is `'0 0 * * *'`)
- 'latest_only' (schedule_interval is `timedelta(hours=4)`)
- 'example_python_operator' (schedule_interval=`None`)
- 'example_xcom' (schedule_interval="`@once`")
This helps us cover different scenarios.
Please take another look. Many thanks.
[ Full content available at:
https://github.com/apache/incubator-airflow/pull/3834 ]
This message was relayed via gitbox.apache.org for [email protected]
