10007 story

[pixiwyn]

Deployment Steps

• Run an environment specific deploy:
  • Use the environment switcher to point to the deploying environment.
  • Run npm run deploy:environment-specific <ENV>
• Run an account specific deploy:
  • Use the environment switcher to point to the deploying environment.
  • Run npm run deploy:account-specific
• Kick off Circle build. (NOTE: First build will FAIL)
  • Copy worker_<DEPLOYING_COLOR>.js.zip and upload a copy as worker_<CURRENT_COLOR>.js.zip to the S3 lambda bucket ${var.dns_domain}.efcms.${var.environment}.us-west-1.lambdas and ${var.dns_domain}.efcms.${var.environment}.us-east-1.lambdas
• Restart Circle build.
• After deployment has finished, subscribe to the new sns topic system_health_alarms in us-west-1.

Rollback Steps (Run these steps in the unlikely event you want to revert the deploy of this story.)

• Switch back to the branch/commit hash that you would like to revert to.
• Run an environment specific deploy:
  • Use the environment switcher to point to the deploying environment.
  • Run npm run deploy:environment-specific <ENV>
• Run an account specific deploy:
  • Use the environment switcher to point to the deploying environment.
  • Run npm run deploy:account-specific
• Kick off Circle build.
• Disengage Maintenance Mode:
  • Use the environment switcher to point to the deploying environment.
  • Run npm run maintenance:disengage <ENV>

[mmarcotte]

Just thinking about this implementation and pattern. Thinking about option enabling architecture could/should the persistence/auth layer handle these exceptions and throw non-Cognito like error messages?

For example,

if (tempPassword) { 
  const { AccessToken, IdToken, RefreshToken } = await applicationContext.getUserGateway().confirmTempUser(email, tempPassword);
  // the above would throw the relavent errors

  // queue work if they're a pendingEmail
} else {
  const { AccessToken, IdToken, RefreshToken } = await applicationContext.getUserGateway().confirmForgotPassword(code, email, password);
  // the above would throw the relavent errors

}

What you have is totally okay for now, but trying to think about potential next steps.

[pixiwyn]

Good observation, we are tackling some of this as a part of DoD here: flexion#10278

[mmarcotte]

whooooah, this is excellent work. thank you for all the hard work.