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?
Show HN: Visualize Airflow's schedule by exporting future DAG runs to GCalendar
11–12 of 12 posts
I run it as a (additional) DAG on Airflow. Take a look at the example script (example.py).
Re: Show HN: Visualize Airflow's schedule by exporting future DAG runs to GCalendar
#12This 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.
Yep, true; how you get the iCalendar file to the user could affect the requirements and experience a lot.
Web could work well for pull-based retrieval, and email's probably a good push option when you have a defined set of recipients.