Narrative downloads no longer working

[briri]

The narrative generator is getting requests from the frontend but it is returning 404 errors for some reason

[briri]

this appears to be due to the fact that the migrated plans do not yet have records in the DynamoDB database.

We have a GraphQL endpoint to create them, but its too much data and killing the application. We will need to create a script that can be run outside the Apollo server process.

We should also add a CloudWatch alarm/event to catch these app shutdowns! https://github.com/cdlib/cdl-web-prd/blob/main/templates/uclib/devRestorer.yaml.j2#L182

[briri]

I think what we need to do is create some AWS Lambda functions to help us process the PlanVersions.

The current setup where the system calls the commonStandardService inline feels a bit fragile, so it would also benefit from this change.

We will want to create a Lambda that:

• Is triggered by an SNS message containing the encrypted access token and and array of plan ids
• Inspects the token and verifies access (the jti from the token can be used to help tie logs from Apollo to the logs generated by the Lambda)
• Looks up the specified plan ids from the RDS MySQL database
• Converts the plans into the common standard
• Updates the DynamoDB table with the new versions

We will then want a Lambda that:

• Is triggered by an SNS message containing the encrypted user token
• Inspects the token and verifies user is super admin
• Fetches plan Ids for every plan that A) has no entry in the DynamoDB table or B) whose modified date does not match the modified date of the latest version.
• Sends an SNS message to trigger the Lambda listed above. These should be batched into sets of 100?

We will then update the Apollo server code to

• Have an SNS messaging service
• Call the 2nd Lambda when from the superInitializePlanVersions resolver
• Call the 1st Lambda from the PlanVersion model's create/update/delete functions

We will also want to add the DMP Common Standard types to the @dmptool/types repo.