Skip to content

Phase 10: Update CI/CD, webhooks, and org secrets #331

Closed

Description

@neuromechanist

Parent Epic

#314

Goal

Update all CI/CD pipelines, GitHub webhooks, and org-level secrets to point to the SCCN account infrastructure.

Tasks

GitHub Actions Deploy Workflows

  • Generate new Cloudflare API token on SCCN account with required permissions (Workers, D1, Pages)
  • Update CI deploy token in GitHub repository settings (development environment)
  • Update any workflow files that reference account-specific IDs
  • Test CI deploy to SCCN account

GitHub Webhooks

  • Update webhook URL on nemarDatasets org from old API URL to api.nemar.org
  • Verify GITHUB_WEBHOOK_SECRET / NEMAR_WEBHOOK_TOKEN match
  • Test webhook delivery (push events, PR events)

Org Secrets (nemarDatasets)

  • Review org-level secrets: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, NEMAR_WEBHOOK_TOKEN
  • Update NEMAR_WEBHOOK_TOKEN if webhook secret changed
  • Verify dataset repo workflows still function (CI validation, PR merge, LLM enrichment)

Catalog Sync Workflow

  • Update .github/workflows/catalog-sync.yml if it references account-specific config
  • Test catalog sync against new backend

Depends On

Notes

  • CF API token needs: Workers Scripts:Edit, D1:Edit, Pages:Edit, Account Settings:Read
  • Per deploy notes: always use npx wrangler@latest and -c backend/wrangler.toml

Activity

  1. neuromechanist commented on Apr 26, 2026

    @neuromechanist
    ContributorAuthor

    Pickup notes for next session

    Priority order

    1. 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.
    2. 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.
    3. 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.
    4. 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).

    Out of scope

  2. neuromechanist commented on Apr 27, 2026

    @neuromechanist
    ContributorAuthor

    Done via #354

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    infrastructureInfrastructure and deployment

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions