NB: archived until there's a consensus on the definition of 'expired' in PROD.

Delete expired Formstack data

This repo provides lambdas which are used for (respectively):

This is to ensure our use of Formstack is GDPR compliant.

Local development

Start Docker if not running, then execute:

source ./scripts/setup

Start Docker if not running, then to get started execute:

./scripts/invoke_lambda -h

Why are there two Formstack accounts?

This was to mitigate against the (historical) limit of 25 users per Formstack account.
If new credentials are required to make authenticated Formstack API calls, who can these be obtained from?

All API calls require an access token; this can be provided by IT Service Desk. GET requests for submissions also require the password that is used to encrypt submissions i.e. the encryption password; this can be provided by Central Production.
There are other Formstack lambdas in the identity-processes repository. Do these make the lambdas in this repo redundant?

No, the Formstack lambdas in the identity-processes repo have separate concerns.
- formstack-consents: lambda which updates identity with consents that were made via Formstack forms
- formstack-baton-requests: responsible for interacting with Formstack to fulfill right-to-erasure and subject-access-requests
Why is this process owned by EdTools?

If no 3rd-party tools were available, then this functionality would be provided by an in-house tool developed and maintained by EdTools.
Why does this sit in the Composer account?

It is related to content creation.