Adds a new Azure Function MappingRules, that generates mapping rules when given a table_id.
The UX change is that reused mapping rules will now be generated when a user selects the Person Id and Date Event for that table, instead of using the "Refresh Rules" button.
This enables larger scan reports, as the workload is now serverless, and only happening on a table basis rather than a whole Scan Report.
The UI has been updated with a notice to reflect this, and removing the "Refresh Rules" button entirely. The JSX changes are mostly Prettier working away.
The code to generate the rules is mostly lift and shift (added docs, types, tests), as we can now use the database directly in Azure functions.
I've moved this code into the shared package, with the intention of removing it from the CLI (which will use the new service), and the existing services_rules.py.
Changes
Adds a new Azure Function
MappingRules
, that generates mapping rules when given atable_id
.The UX change is that reused mapping rules will now be generated when a user selects the Person Id and Date Event for that table, instead of using the "Refresh Rules" button. This enables larger scan reports, as the workload is now serverless, and only happening on a table basis rather than a whole Scan Report.
The UI has been updated with a notice to reflect this, and removing the "Refresh Rules" button entirely. The JSX changes are mostly Prettier working away.
The code to generate the rules is mostly lift and shift (added docs, types, tests), as we can now use the database directly in Azure functions. I've moved this code into the shared package, with the intention of removing it from the CLI (which will use the new service), and the existing
services_rules.py
.Closes #663 Closes #612
Screenshots
Deployment
Needs the following environment variables added:
A new
MappingRules
queue for:Checks
Important: please complete these before merging.
changelog.md
, including migration instructions if any.