dpsctl verify
dpsctl verify Usage Guide
Verify DPS deployment status and component connectivity.
Usage
dpsctl verify [options]
Flags
Includes global dpsctl options.
--{{ .Site.Params.ProjectShortNameLower }}-server Check only {{ .Site.Params.ProjectShortName }} Server accessibility (default: check all components)
--database Check only database accessibility (default: check all components)
--auth Check only authentication service (default: check all components)
--ui Check only UI accessibility (default: check all components)
--bcm Check only BCM connectivity (default: check all components)
--help, -h show help
Examples
Verify All Components
$ dpsctl verify
{
"dps_server": {
"status": "ok",
"message": "DPS server is accessible"
},
"database": {
"status": "ok",
"message": "Database connection successful"
},
"auth": {
"status": "ok",
"message": "Authentication service is working"
},
"ui": {
"status": "warning",
"message": "UI is accessible but some features may be limited"
},
"bcm": {
"status": "error",
"message": "BCM connection failed: connection timeout"
}
}
Verify Specific Component
$ dpsctl verify --{{ .Site.Params.ProjectShortNameLower }}-server
{
"dps_server": {
"status": "ok",
"message": "DPS server is accessible"
}
}
Verify Multiple Components
$ dpsctl verify --{{ .Site.Params.ProjectShortNameLower }}-server --database
{
"dps_server": {
"status": "ok",
"message": "DPS server is accessible"
},
"database": {
"status": "ok",
"message": "Database connection successful"
}
}
Notes
- If no specific component flags are provided, all components are checked by default
- Useful for deployment validation and troubleshooting
- Each component check is independent and failures are reported separately
- Status values can be:
ok,warning,error