You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Phase 10: Update CI/CD, webhooks, and org secrets #331
catalog-sync.yml — PROD_API_URL: https://api.osc.earth/nemar and DEV_API_URL: https://nemar-api-dev.shirazi-10f.workers.dev both still point at the personal account. The workflow needs a SCCN equivalent so the catalog stays fresh on api.nemar.org independent of the legacy redirect. Either add SCCN URLs as additional targets (belt and suspenders during transition) or flip the existing ones over outright.
GitHub webhooks on the nemarDatasets org currently target the personal worker. Repoint to api.nemar.org/webhooks/*. Verify GITHUB_WEBHOOK_SECRET matches between the org-level secret NEMAR_WEBHOOK_TOKEN and the SCCN worker secret.
CI deploy token — generate a new SCCN-account Cloudflare API token (Workers Scripts:Edit, D1:Edit, Pages:Edit) and replace the existing token in the GitHub repo secrets used by deploy-backend.yml. The current token still uses the SCCN account but was last rotated during Phase 4; verify scopes are sufficient.
Org secrets review on nemarDatasets — AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, NEMAR_WEBHOOK_TOKEN. Should be unchanged (S3 bucket and IAM are unchanged), but verify dataset-repo CI workflows still function end-to-end against the SCCN worker.
Context that already exists
SCCN worker live at api.nemar.org and nemar-api.sccn-org.workers.dev.
All 16 Workers secrets mirrored in Phase 4 (Resend domain verified, EZID creds, OpenRouter, etc).
D1 prod data parity confirmed pre-Phase-8 (1 known catalog row drift, self-heals).
Activity
neuromechanist commentedon Apr 26, 2026
Pickup notes for next session
Priority order
catalog-sync.yml—PROD_API_URL: https://api.osc.earth/nemarandDEV_API_URL: https://nemar-api-dev.shirazi-10f.workers.devboth still point at the personal account. The workflow needs a SCCN equivalent so the catalog stays fresh onapi.nemar.orgindependent of the legacy redirect. Either add SCCN URLs as additional targets (belt and suspenders during transition) or flip the existing ones over outright.nemarDatasetsorg currently target the personal worker. Repoint toapi.nemar.org/webhooks/*. VerifyGITHUB_WEBHOOK_SECRETmatches between the org-level secretNEMAR_WEBHOOK_TOKENand the SCCN worker secret.deploy-backend.yml. The current token still uses the SCCN account but was last rotated during Phase 4; verify scopes are sufficient.nemarDatasets—AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY,NEMAR_WEBHOOK_TOKEN. Should be unchanged (S3 bucket and IAM are unchanged), but verify dataset-repo CI workflows still function end-to-end against the SCCN worker.Context that already exists
api.nemar.organdnemar-api.sccn-org.workers.dev.Out of scope
Phase 10: flip CI/CD to SCCN account (#331) (#354)
neuromechanist commentedon Apr 27, 2026
Done via #354