sandbox · example data only · not your workspace
← all scenarios

DevOps Pipeline Demo

Connect GitHub → DevOps Engineer reads pipeline → explains failure → suggests fix.

DevOps Engineer reads-only at first. Modifying the pipeline requires approval.

Steps
5
Est. time
~6 min
Audience
public
Reviewed
2026-05-23
engineer · DevOps Engineerconnector · GitHub

data flow

scenario architecture


   GitHub  ──webhook──▶  DevOps Engineer  ──read pipeline──▶  status
                                │
                            explain failure (cite log lines)
                                │
                            suggest diff
                                │
                                ▼
                        two-person approval  ──tip──▶  open PR
step 1/5·No approval needed

Connect GitHub

OAuth or PAT.

visionxixlabs.com/dashboard/integrations/github
AAxiom
Sign out

connectors · GitHub primary

GitHublive
· auth · OAuth app · repo + workflow scopes (read-only at install)
· region ·
· 12 repos linked
· last sync · 12s ago
invariantNo long-lived access keys stored. AWS assumes a role you create with an externalId we generate; Azure uses a service principal you control. You can revoke from the provider console without telling us.

Assume-role over keys

Cloud connectors never store long-lived access keys. AWS uses a cross-account IAM role you create + an externalId we generate; Azure uses a service principal you control. You can revoke at any time from the provider console — no calls needed.

safety invariants in play

  • Assume-role model No long-lived access keys stored — workspace assumes a short-lived role you own and can revoke.

expected result

Repos visible in DevOps overview.

engineering principle

DevOps Engineer is read-only by default. Modifying the pipeline (yaml, secrets, branch protection) is always change-class — same approval rule as a Terraform apply, same audit fabric.