Skip to content

Correctly handle data-loss scenarios when encrypting columns

What does this MR do?

If the EncryptColumns background migration runs in a sidekiq with a stale view of the database schema, or when the purported destination columns don't actually exist, data loss can result.

Attempt to work around these issues by reloading schema information before running the migration, and raising errors if the model reports that any of its source or destination columns are missing.

What are the relevant issue numbers?

Closes #53763 (closed)

Does this MR meet the acceptance criteria?

Edited by Nick Thomas

Merge request reports

Loading