DEVOPS
Weekly base-image EOL posture snapshot to BigQuery
Compiles a weekly inventory of every base image in use with its support status and days-to-EOL, writes the snapshot to BigQuery for trend tracking.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts the posture snapshot
- ActionEnumerate base images across tracked GitHub reposGitHub
- ActionResolve EOL dates and compute days remaining over HTTPHTTP webhook
- LogicBucket images into supported, near-EOL, and EOL
- ActionAppend the timestamped snapshot to BigQueryBigQuery
- OutputRender a leadership trend summary in NotionNotion
What it does
This workflow turns base-image EOL data into a tracked metric. Each week it inventories every base image across your repos, computes days remaining until EOL, and appends a timestamped snapshot to a BigQuery table so you can chart whether your fleet's support posture is improving or decaying over time.
When to use it
Use this when you need to report supply-chain hygiene to leadership or prove progress against a remediation goal. The historical snapshots let you show the count of EOL and near-EOL images trending down quarter over quarter.
How it works
- 1A weekly schedule starts the snapshot.
- 2The workflow enumerates base images across the tracked GitHub repos.
- 3It resolves each image's EOL date over HTTP and computes days remaining.
- 4A logic step buckets images into supported, near-EOL, and EOL categories.
- 5It appends the full timestamped snapshot to a BigQuery table.
- 6It renders a leadership summary with the week's bucket counts and trend to a Notion page.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect BigQueryDatasets, queries, schemas.
- 4Connect NotionPages, databases, comments.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.