DEVOPS
Block EOL base images at registry push time
Triggers on a registry image-push webhook, inspects the pushed image's base layer support status.
How it runs
The automated pipeline, trigger to output.
- TriggerRegistry image-push webhook firesHTTP webhook
- ActionInspect the pushed image manifest for its base layerHTTP webhook
- LogicDecide pass or fail on base-layer support status
- ActionOpen a rebuild issue for the owning team on failGitHub
- OutputPost the pass/fail verdict to SlackSlack
What it does
The moment a new image is pushed to your registry, this workflow inspects its base layer and checks whether that base is still supported. It gives an immediate verdict so a freshly built image on an already-dead base never quietly becomes the new baseline.
When to use it
Use this as a shift-left guardrail in CI/CD. Catching an EOL base at push time is far cheaper than discovering it weeks later during an incident, and it keeps teams from rebuilding on stale parent images out of habit.
How it works
- 1A registry push webhook fires with the new image reference.
- 2The workflow inspects the image manifest over HTTP to extract the base layer and tag.
- 3It queries the EOL data source for that base's support window.
- 4A logic step decides pass (supported) or fail (EOL or near-EOL).
- 5On fail it opens a GitHub issue assigning the image's owning team to rebuild.
- 6Either way it posts the verdict to Slack so the pushing engineer sees it right away.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.