Live data from Hacker News

Show HN: Visualize Airflow's schedule by exporting future DAG runs to GCalendar

github.com

1–10 of 12 posts

Re: Show HN: Visualize Airflow's schedule by exporting future DAG runs to GCalendar

#3
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.

Re: Show HN: Visualize Airflow's schedule by exporting future DAG runs to GCalendar

#9
This looks very neat!

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].

[1] - https://icalendar.readthedocs.io/en/latest/usage.html#exampl...

[2] - https://en.wikipedia.org/wiki/ICalendar#Distributing_updates

Re: Show HN: Visualize Airflow's schedule by exporting future DAG runs to GCalendar

#10
post #9

This looks very neat! 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…

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.
Post reply on HN