Ensure future cached data mismatch issues are caught in staging
gitlab-com/gl-infra/production#6372 (closed) happened because there were existing cached broadcast messages in production but not in staging. When a new attribute was added to broadcast messages, new code that tried to access the new attribute (that had default value in DB) from cached data received nil
values instead of the default value.
Action items
To prevent similar issues in the future we will do the following:
-
Create cached active broadcast messages (banner & notification types) in staging environment
Edited by Eugie Limpin