Show HN: Visualize Airflow's schedule by exporting future DAG runs to GCalendar (github.com)

Brilliant! Each item could include a meeting link to debug the failed part together :) Perfect for the remote-first world.

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.

Apache Airflow DAG = Directed Acyclic Graph

https://airflow.apache.org/docs/stable/concepts.html

In case you were also wondering what this item is about and came to the comments first.

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.

Airflow is _the worst_

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?

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