Feature: dynamodb migration about nshm-toshi-api

[chrisbc]

Phase 2 deployment plan...

Rollback

• use S3 Backup if needed (only if new S3 objects were created)
• TUI rollback deployment merge
• ToshiAPI rollback deployment merge

Pre-requisites

• backup S3
• ensure the are no existing Toshi Tables in AWS

deploy upgrade ToshiAPI to test.

• promote all TUI changes in deploy-test to PROD
• merge API update to TUI (TEST)
• deploy new ToshiAPI (TEST)
  • hit serverless_requirement issue so deployed stack locally wiht sls deploy --stage test
• update new TEST API keys (Toshi UI)
• update new TEST API keys (Secrets Manager)

Read-only tests (checks legacy)

• manually test on TUI READ operations
• verify cloudwatch metrics OK
• verity API logs OK

Create + read tests (checks Dynamodb R/W)

• using Runzi + AWS + TUI:
  • new Rupture sets OK
  • check new tables + CW metrics look good
  • new ruptset diags OK
  • run inversions OK
  • run inversion Haz OK
  • run inversion diags OK
  • run inversion analysis OK (Solvis API)
  • check new tables + CW metrics look good (2nd take)