Diagnostics
ske doctor checks your environment’s connectivity, permissions, and configuration in one pass.
Running diagnostics
Section titled “Running diagnostics”ske doctor --env production SKE Doctor — production
✓ API reachable ✓ Authentication valid ✓ Organization access ✓ Workspace access ✓ Project found ✓ Environment found ✓ Cloud provider connected ✓ Cloud provider credentials valid ✓ Container registry accessible ✓ Database reachable ✓ Cache reachable ✓ Queue configured ✓ Domain certificate valid ✗ PHP extensions — missing ext-redis
13/14 checks passedWhat doctor checks
Section titled “What doctor checks”| Check | What it verifies |
|---|---|
| API reachable | Can reach the SKE API |
| Authentication | Access token is valid and not expired |
| Organization access | Current user has access to the organization |
| Workspace access | Current user has access to the workspace |
| Project found | The project in ske.yml exists |
| Environment found | The target environment exists |
| Cloud provider | Provider credentials are valid and connected |
| Container registry | Can authenticate to ECR/Artifact Registry |
| Database | Database instance is running and reachable |
| Cache | Cache instance is running and reachable |
| Queue | Queue infrastructure is provisioned |
| Domain certificate | SSL certificate is issued and valid |
| PHP extensions | Required extensions are available |
| Token scope | API token (if using SKE_API_TOKEN) has sufficient permissions |
Using doctor for troubleshooting
Section titled “Using doctor for troubleshooting”Deployment failures
Section titled “Deployment failures”If ske deploy fails, run ske doctor first to check prerequisites:
ske doctor --env productionCommon issues doctor catches:
- Expired or invalid cloud provider credentials
- Missing IAM permissions for new features
- Network connectivity issues between compute and database/cache
- Container registry authentication failures
After infrastructure changes
Section titled “After infrastructure changes”After modifying your cloud provider’s IAM role or GCP service account, run doctor to verify:
ske doctor --env productionCI pipeline verification
Section titled “CI pipeline verification”Add ske doctor as a pre-deploy step in CI:
# GitHub Actions example- name: Verify SKE environment run: ske doctor --env production --json env: SKE_API_TOKEN: ${{ secrets.SKE_API_TOKEN }}The --json flag outputs structured results for programmatic checks.