DevOps Pipeline Demo
Connect GitHub → DevOps Engineer reads pipeline → explains failure → suggests fix.
DevOps Engineer reads-only at first. Modifying the pipeline requires approval.
data flow
scenario architecture
GitHub ──webhook──▶ DevOps Engineer ──read pipeline──▶ status
│
explain failure (cite log lines)
│
suggest diff
│
▼
two-person approval ──tip──▶ open PRConnect GitHub
OAuth or PAT.
connectors · GitHub primary
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.