Skip to content

Latest commit

 

History

History
34 lines (20 loc) · 1.12 KB

UPGRADE.md

File metadata and controls

34 lines (20 loc) · 1.12 KB

Upgrades/Migrations

This document will describe the necessary steps to migrate existing deployments through versions of FAIMS.

Upgrading from v1 to v1.1

Upgrade summary

TBD - currently there are the following migrations needed.

Pull request migrations

The following pull requests introduced breaking changes/migrations:

feat: admin forgot password reset workflow

CouchDB migration

This functionality will not work until you apply the following migration

  • login as cluster admin to old conductor
  • copy the bearer token
  • update /api/.env with USER_TOKEN=<>
  • setup npm env cd /api && npm i
  • run the force init action npm run forceinitdb
  • Try generating a code and make sure the workflow is functional.

Deployment configuration

Add the new NEW_CONDUCTOR_URL environment variable to the conductor/api build. This is already done in the aws-cdk IaC - however in existing deployments you may need to update your build configuration.

Note ensure this includes the https:// prefix!

This is a mandatory property and not including it will break the deployment.