This looks very neat!<p>Just a thought - one that could involve implementation challenges and/or require too much effort to be worthwhile:<p>It might be possible to generate iCalendar-format schedules, which could widen compatibility and ease up the access permissions concerns you mention in the readme.<p>Python has a decent icalendar[1] library - and updates to existing entries be handled by ensuring that the ID for each schedule object is stable when updates are distributed[2].<p>[1] - <a href="https://icalendar.readthedocs.io/en/latest/usage.html#example" rel="nofollow">https://icalendar.readthedocs.io/en/latest/usage.html#exampl...</a><p>[2] - <a href="https://en.wikipedia.org/wiki/ICalendar#Distributing_updates" rel="nofollow">https://en.wikipedia.org/wiki/ICalendar#Distributing_updates</a>
Believe it could be also relatively easy to adapt it to other scheduling solutions. As long as schedule expression and job/DAG run history and can be provided that is.
Apache Airflow DAG = Directed Acyclic Graph<p><a href="https://airflow.apache.org/docs/stable/concepts.html" rel="nofollow">https://airflow.apache.org/docs/stable/concepts.html</a><p>In case you were also wondering what this item is about and came to the comments first.
This is great work, I love how it's basically using gcal as a rendering engine.<p>We are building something similar for Cronitor that will work for any kind of scheduled job. If anybody is interested in beta testing or hearing more I would love to chat.
Hello, thanks for open sourcing this terrific project. I like the idea but am a little confused about usage. How do you recommend monitoring existing pipelines, with an additional pipeline or by modifying the existing one?