These lambdas relate to automated tasks, usually run on a daily basis, which copy promotions data stored in the DynamoDB tables over to SalesForce and BigQuery, as well as backing up the DB tables themselves.
Five lambda functions are defined in the lambdas/src folder. They relate to eight lambdas in AWS, in the memsub-promotions-lambdas application - link here: https://eu-west-1.console.aws.amazon.com/lambda/home?region=eu-west-1#/applications/memsub-promotions-lambdas
We can also list just the Lambdas in AWS using this link: https://eu-west-1.console.aws.amazon.com/lambda/home?region=eu-west-1#/functions?fo=and&k0=functionName&o0=%3A&v0=MembershipSub
We can view the DynamoDB tables at this link (search on ‘prom’): https://eu-west-1.console.aws.amazon.com/dynamodbv2/home?region=eu-west-1#tables
A Lambda function to replicate the MembershipSub-PromoCode-View-CODE Dynamo table to Salesforce.
This lambda sends data to salesforce on a daily schedule. We can just check the lambda's cloudwatch logs to confirm that it's happy - it logs all the requests it's making.
Two versions of this lambda (PROD, CODE) exist in AWS, each of which maps to the equivalent environment in the SalesForce cloud. We can use the CODE version for testing.
The lambda relies on SalesForce usernames/passwords which have been stored in AWS as encrypted environment variables.
Only the PROD will rebuild automatically when a PR branch merges into main.
An Amazon DynamoDB trigger that creates a view of data associated with a particular promo code for the data pipeline to collect.
The code writes updates from the Promotions table to the PromoCode-View table.
During development work, we can test by creating a test promotion in the Promo Tool (this repo's frontend) in its CODE page and check that it gets written to PromoCode-View-CODE table.
Two versions of this lambda (PROD, CODE) exist in AWS. We can use the CODE version for testing. Only the PROD will rebuild automatically when a PR branch merges into main.
This lambda appears to be for rebuilding the MembershipSub-PromoCode-View table. The intention is for it to be run manually if that is ever required -
Because these are lambdas, we cannot develop and test on local devices. Instead code needs to be written locally and then all the lambda files in the lambdas/source folder (but not the folder itself, or any subfolders) need to be zipped and uploaded manually - using the AWS lambdas console - for testing.
The deploy is called MemSub::Membership Admin::Promotions Tool Lambda
Note that only the PROD versions of the lambdas will automatically rebuild. The CODE version needs to be updated manually in the AWS lambdas console