Skip to content
This repository was archived by the owner on Jan 9, 2024. It is now read-only.

MIGRATE_TESTING.md

Latest commit

 

History

History
35 lines (21 loc) · 1.21 KB

MIGRATE_TESTING.md

File metadata and controls

35 lines (21 loc) · 1.21 KB

Testing a Bootstrap v1 to v2 Migration

With the steps below, you can test a v1 to v2 Bootstrap Migration using a secondary test Stedi account.

  1. Setup the .env with just a STEDI_API_KEY for the source account.

  2. Create a backup of partners-configuration and Guides by running:

npx ts-node-esm ./src/scripts/backup.ts

  1. Change your .env to another API key for your target empty test account.

  2. Restore the un-migrated Stash config (and Guides) by running:

npx ts-node-esm ./src/scripts/restore.ts

  1. Update at least one profile from each partnership in the partners-configuration Stash keyspace to include coreProfileType: "local" so the migration script can correctly identify the local profile.

  2. Run the migration script:

npm run migrate
  1. Ensure you change any destination webhooks before testing end-to-end flows.

Note about failures

  • If the migration fails for any reason, delete any Profiles and/or Partnership records created by the early migration attempt in the Partners UI, but you attempt to retry it.

  • The unneeded Stash records will only be destroyed if the entire migration as been successful, so failed migrations can be retried without a restore.