Split reads for new group and instance Microsoft Applications tables
What does this MR do and why?
Split reads for new group and instance Microsoft Applications tables
We've recently completed a data migration for the
system_access_microsoft_applications table and related tables. This MR
implements the second half of the transition to the two tables, allowing
reading off the new table for specific groups, controlled by a feature
flag.
During the transition, new records and updates to the Microsoft Applications table are written to both new and legacy tables, so we can seamlessly enable and disable the feature flag. When the transition is complete, we can remove the feature flag and drop the legacy data.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
- Original issue: #495499 (closed)
- This MR implements issue: #495500 (closed)
- Data migration MR: !177531 (merged)
- Rollout issue for FF: #512497 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
No user-visible changes
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #495500 (closed)