Skip to content

feat(blob): decommission old ocobo-blob store from personal account #199

Description

@wab

Parent

Milestone #3 — Blob migration follow-up: cutover and cleanup

What to build

Delete the ocobo-blob store from the personal "wab" Vercel account once production is confirmed green on the new website-blob store. HITL — manual action in the Vercel dashboard.

Wait at least one full deployment cycle (24 h+) after #196 lands to allow any latent reference to surface. Smoke-test everything once more before pressing delete.

Steps:

  1. Confirm production has been green on new store for at least one deployment cycle.
  2. Vercel dashboard → "wab" personal account → Storage → ocobo-blob → Delete Store.
  3. Remove the old BLOB_READ_WRITE_TOKEN value from posts/.env.local (and clean up NEW_BLOB_READ_WRITE_TOKEN if it was kept dual, renaming the new one to the canonical BLOB_READ_WRITE_TOKEN).
  4. Confirm no environment variable in either Vercel project still references the old store's token.

Acceptance criteria

  • Production smoke-test green for ≥ 1 full deployment cycle on new store
  • ocobo-blob deleted from "wab" personal account
  • Old BLOB_READ_WRITE_TOKEN value removed from posts/.env.local
  • New token canonicalised (renamed to BLOB_READ_WRITE_TOKEN if it was dual-named)
  • No Vercel project env var still references the old token

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions