Critical infrastructure use case · GitHub + ArgoCD + ServiceNow
Deployment governance
Deployments and change records are kept separately, so proving a deployment was approved takes effort. Every deployment links to an approved change, passing checks and a deployment event.
Systems involved
What each system contributes
Trigger integration
Events start or continue the run.
GitHub provides repository search and check errors as pre-built actions. Other GitHub operations use the GitHub API or Rules + Code. ArgoCD is a trigger integration.
Architecture
One governed run
How it starts: An approved ServiceNow change starts the run. GitHub and ArgoCD events start the follow-up legs.
Step by step
How the process runs
- 01
Change
An approved ServiceNow change starts the run.
- 02
Checks
GitHub check errors and repository search confirm readiness.
- 03
Deploy event
An ArgoCD event starts post-deployment verification.
- 04
Evidence
The change record is updated and closed.
Control
Human decision and exception path
Human decision
Deployment proceeds only against an approved change.
Exception path
- Failing checks stop the run.
- Missing deployment events raise an alert.
- Unlinked deployments open a ticket.
Evidence
What gets audited
- Change approval.
- Check results.
- Deployment event.
- Closure.
Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.
The linked record can support evidence for NIS2 change management expectations.
Sovereignty and deploymentRelated
Patterns, connectors and next steps
- GitHub connector
2 pre-built actions
- ArgoCD connector
Trigger integration
- ServiceNow connector
55 pre-built actions
- Infrastructure orchestration
Operations runbooks with approval and evidence.
- Infrastructure alert to incident and remediation
Another critical infrastructure use case.
FAQ
Questions about this use case
- Does Nexus replace any of these systems?
- No. Each system keeps its own records. Nexus runs the process between them and records each decision.
- How does the run start?
- An approved ServiceNow change starts the run. GitHub and ArgoCD events start the follow-up legs.
- What if a step is not covered by a pre-built action?
- GitHub provides repository search and check errors as pre-built actions. Other GitHub operations use the GitHub API or Rules + Code. ArgoCD is a trigger integration.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.