Architect mechanism for cleaning app metadata when a customer uninstalls an app

[plittlewood-rpt]

Background context AppMarket apps can write store own metadata against Platform entities. This is a useful feature and allows our entities to be extended to suit a particular app's purpose and needs. Currently, this data is stored perpetually even after a customer uninstalls the app. We should consider an appropriate cleanup mechanism for this data to limit our data storage costs, bearing in mind that it's perfectly feasible that a customer might reinstall the same app later, so there will need to be a window before any cleanup routines run after an app is initially uninstalled

Specification

• Review the metadata Dynamo table design
• Decide on the most performant way of locating metadata that belongs to a particular customer and app. It is vital that only data belonging to a particular customer/app pair is deleted, and not ALL that app's data (other customers will still have it installed)
• A Lambda function (or set of functions) might be the best use case here, as these can be triggered on a certain schedule. Consider the maximum execution time against the DynamoDb search operation
• Put together a high level plan of what the function or service would do including
• -- How it will decide which data to look for
• -- The frequency at which the job should run
• -- Any logging that might be appropriate
• -- Any backup mechanisms that might be appropriate
• -- The execution flow
• Another option to consider could be to leverage the DynamoDb TTL functionality. Initially this would be left empty (if this is supported) to signal that the record should live indefinitely. At the point an app is uninstalled a job could run that sets the TTL for today + n months. DynamoDb can then be the thing that manages the physical deletion of that data
• Remember that this is a research ticket. Circulate plan to wider group for discussion, after which any implementation tickets will be logged to break the work up into manageable items

[github-actions[bot]]

We need to research or gather more information relating to this request. We have moved this issue into our ‘Not Ready’ column whilst we obtain the information required. For more information on our processes, please click here

[github-actions[bot]]

Whilst the nature of this request has been accepted, we are unable to commit to a specified sprint and therefore have assigned this issue to the ‘Long Term’ column (typically completed 9+ months). We will regularly review any issues and where development capacity is available, or work is aligned with our Roadmap, the issue will be updated. For more information on our processes, please click here