What if we merely add a property "run_date" to DagRun? At present
this would be essentially same as "next_execution_date".
Then no change to scheduler would be required, and no new dag parameter or
config. Perhaps you could add a toggle to the DAGs UI view that lets you
choose whether to display
It is deployed from https://github.com/apache/airflow-site?files=1
On 3 September 2019 20:22:37 BST, Jarek Potiuk wrote:
>I believe it is fully automated during the release but it only shows
>the
>last stable release ("1.10.4" in this case). The "master" changes are
>visible in readthedocs in "la
Hello,
We use gitpubsub to sync apache/airflow-site with apache server
https://github.com/apache/airflow-site
We don't use readthedocs to deploy documentation to
airflow.apache.org. RTD is an independent service not associated with
our site.
K.
On Tue, Sep 3, 2019 at 9:22 PM Jarek Potiuk wrote
I believe it is fully automated during the release but it only shows the
last stable release ("1.10.4" in this case). The "master" changes are
visible in readthedocs in "latest" version:
https://airflow.readthedocs.io/en/latest/howto/index.html . That's probably
where the changes you refer to are v
Hi everyone,
Can anyone help me figure out what is the process of deploying the
https://airflow.apache.org/ website?
I have noticed that few changes that we pushed recently haven't appeared
yet.
Thanks,
Aizhamal
