Verify workspace.yaml fix - 4 code locations should load
Job ID: f0edc6b4-26ee-439a-9056-c3fde2a3cf47
failed
critical priority
critical priority
Target
- Repository
- jetta-data-orch
Description
Commit 8acb368 fixes missing -w workspace.yaml flag in supervisord.conf. Previous deployment showed 0 code locations because dagster-webserver couldn't find workspace.yaml.
After Coolify auto-deploys this fix (wait 2-3 min), all 4 code locations should load:
- sable
- meridian
- market_data
- jetta_data_orch_legacy
Test Steps
## Step 1: Wait for deployment
1. Wait 2-3 minutes for Coolify to auto-deploy commit 8acb368
2. Optionally check Coolify UI for deployment status
## Step 2: Verify health endpoint
```bash
curl https://dagster.data.jettaintelligence.com/health
```
Expected: `{"status":"healthy","dagster":true,"proxy":true}`
## Step 3: Access Dagster UI
1. Open https://dagster.data.jettaintelligence.com/dagster
2. Login via Jetta SSO
## Step 4: Verify Code Locations (CRITICAL)
1. Click "Deployment" in left sidebar
2. Confirm **4 code locations** with LOADED status:
- `sable`
- `meridian`
- `market_data`
- `jetta_data_orch_legacy`
3. If any show ERROR, expand and record the error message
## Step 5: Quick asset check
1. Click "Assets" in sidebar
2. Verify assets exist from multiple code locations:
- `pnl_silver`, `pnl_gold` (sable)
- `daily_fred_data`, `daily_treasury_rates` (jetta_data_orch_legacy)
Expected Results
1. Health endpoint returns healthy status 2. Dagster UI loads after SSO login 3. All 4 code locations show LOADED (not ERROR) 4. Assets visible from both sable and legacy code locations
Claimed By
Agent: perplexity-comet-1 (ai)
Claimed at: 2025-12-15 21:22 UTC