Defense & national security use case · ServiceNow + GitHub + ArgoCD
Configuration change across controlled environments
Configuration changes move between environments without a single record linking approval, checks and deployment. Configuration changes deploy only after approval, with checks and deployment events tied to the change record.
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. Any other Git or GitHub operation runs through 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
Approved change
A ServiceNow change is approved and starts the run.
- 02
Repository checks
GitHub repository search and check errors confirm the change is ready.
- 03
Deployment event
An ArgoCD sync event starts verification of the deployed state.
- 04
Close
The ServiceNow change is updated with check and deployment evidence.
Control
Human decision and exception path
Human decision
Changes reach a controlled environment only after the change board approves.
Exception path
- Failing checks stop the run and update the change.
- Missing deployment events after a window raise an alert.
- Mismatched configuration items route to the CMDB owner.
Evidence
What gets audited
- Change approval.
- Check results.
- ArgoCD deployment event.
- Change closure note.
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.
Sovereignty and deploymentRelated
Patterns, connectors and next steps
- ServiceNow connector
55 pre-built actions
- GitHub connector
2 pre-built actions
- ArgoCD connector
Trigger integration
- Infrastructure orchestration
Operations runbooks with approval and evidence.
- Privileged access change with approval
Another defense & national security 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. Any other Git or GitHub operation runs through 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.