Keep every deployment on a supported runtime version
Every Monday, WebRun opens Astronomer, reads the Astro Runtime version on every deployment across your workspaces, works out how far behind each one is, weights them by how many DAGs they carry, posts the picture to Slack, and drafts an upgrade plan in Gmail for the platform lead.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track which deployments are on an old runtime version?
Every Monday WebRun signs into Astronomer and records the Astro Runtime version on every deployment across your workspaces, comparing each against the newest available. It posts the deployments falling behind to Slack, weighted by DAG count, and drafts an upgrade plan in Gmail for the platform lead to schedule.
- Deployments drifting onto old runtimes are named every Monday
- Upgrade order is weighted by DAG count rather than guessed
- Upgrades get scheduled with a window instead of forgotten
Built for data platform teams · data engineers · analytics engineering leads · DevOps
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
cloud.astronomer.ioin a real browser with your saved login - no setup, no API keys. -
1
Astronomer - read runtime versions per deployment
astronomer.io
WebRun opens Astronomer to read runtime versions per deployment. - Sign in to Astronomer and list the deployments in each workspace you own
- Record the Astro Runtime version running on every deployment
- Compare each against the newest version available in your account
- Count the DAGs on each deployment so the busiest ones are weighted first
- Read the deploy history to see when each was last updated
- Never trigger a deploy or an upgrade: WebRun reads and reports only
Done when Every deployment has its runtime version, DAG count and last deploy date recorded.
-
2
Slack - post the deployments falling behind
slack.com How to Automate Slack
WebRun opens Slack to post the deployments falling behind. - Post the deployments running behind the newest runtime, furthest behind first
- Show the DAG count beside each one so impact is obvious
- Note deployments that have not been deployed to in months
- Say clearly when everything is current, so a clean week is still reported
Done when The data platform channel has this week's runtime picture.
-
3
Gmail - draft the upgrade plan
gmail.com How to Automate Gmail
WebRun opens Gmail to draft the upgrade plan. - Draft an email to the platform lead proposing an upgrade order
- Put the deployments furthest behind and carrying the most DAGs at the top
- Suggest a maintenance window for each, based on when its DAGs are quietest
- Leave the email as a draft. The platform lead reviews, schedules and sends, WebRun upgrades nothing
Done when An upgrade plan is waiting as a Gmail draft.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it upgrade a deployment on its own?
No. WebRun reads versions and drafts a plan. Every upgrade and deploy is triggered by an engineer, because a runtime change on a live deployment needs a chosen window.
How does it decide the upgrade order?
By how far behind the newest available runtime each deployment is, weighted by the number of DAGs it carries, so the busiest deployment on the oldest version is proposed first.
Does it touch any DAG code?
No. It counts DAGs to weight the ranking and never opens, edits, pauses or triggers one. The repository and the schedules are untouched.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.