You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could be discovery or just notes in a doc about future possibilities.
There have been ideas about detecting all migrations, or targeting risky migrations, etc.
a. A risky migration might be one that touches any of our large tables, or makes certain types of changes.
b. For blue/green code/migration changes, can we detect when changes are made in a single deployment that should be across deployments?
Could we detect new toggles to ensure we want the default value? We had an incident where we didn't want the default, but it is what we got.
The text was updated successfully, but these errors were encountered:
robrap
changed the title
Detect risky changes
Detect risky edxapp code changes
Aug 7, 2024
This could be discovery or just notes in a doc about future possibilities.
a. A risky migration might be one that touches any of our large tables, or makes certain types of changes.
b. For blue/green code/migration changes, can we detect when changes are made in a single deployment that should be across deployments?
The text was updated successfully, but these errors were encountered: