DEVOPS
Validate flag MRs against live Vercel state before merge
When a merge request edits flags.json, validates the proposed flags against the live Vercel Edge Config and schema rules.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened or updated webhookGitLab
- LogicFilter: MR modifies flags.json
- ActionFetch proposed flags + live Edge ConfigVercel
- LogicValidate schema, compute intended diff
- OutputPost preflight approve/block comment on MRGitLab
What it does
Gives reviewers a preflight check before a flag change merges. When an MR touches `flags.json`, it parses the proposed flags, validates them against schema rules (valid keys, allowed value types, no orphaned references) and compares the intended change to the current live Vercel Edge Config so reviewers see exactly which keys will flip and by how much. It posts a structured comment on the MR marking it safe or flagging conflicts.
When to use it
Use it as a required check in your flag-change review flow so risky edits, malformed JSON, or surprise overwrites of recently-changed live values get caught at review time instead of after deploy.
How it works
- 1A GitLab merge-request webhook triggers on open and update events.
- 2A logic step filters to MRs that modify `flags.json`.
- 3Fetch the proposed `flags.json` from the MR source branch and read the current live values from the Vercel Edge Config.
- 4A logic step validates schema and computes the intended diff, flagging malformed entries or clobbered live changes.
- 5Post an approve-or-block preflight comment back on the GitLab MR with the diff and any warnings.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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-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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.