Just a thought - one that could involve implementation challenges and/or require too much effort to be worthwhile:
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.
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].
iCalendar is a pretty nice format to use and well supported, but the trouble that you then need a website to host the iCalendar file. It adds more yak-shaving to the process.
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?
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.
This is great work, I love how it's basically using gcal as a rendering engine.
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.
