Different approach to migrate from attr_encrypted to Rails 7/Ruby 3 encryption #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just a special branch of which permits the gems usage in conjunction with Rails 7 encryption/Ruby 3 to facilitate backfill. Parts pulled from a few other forks. This facilitates the UW way of migrating off of the gem which involves the following model concern. The difference is we don't hack together our own implementation or Rails 7 encryption and get the benefit of compression (i.e. let rails do its thing)
This branch probably won't be merged. The latest usable package of this is : 3.1.0.pre.0a24053
Such that given a model with attr_encrypted column of ssn, we'd adjust like so: