README.md in kms_encrypted-1.5.1 vs README.md in kms_encrypted-1.6.0
- old
+ new
@@ -12,11 +12,11 @@
Supports [AWS KMS](https://aws.amazon.com/kms/), [Google Cloud KMS](https://cloud.google.com/kms/), and [Vault](https://www.vaultproject.io/)
Check out [this post](https://ankane.org/sensitive-data-rails) for more info on securing sensitive data with Rails
-[](https://github.com/ankane/kms_encrypted/actions)
+[](https://github.com/ankane/kms_encrypted/actions)
## How It Works
This approach uses a key management service (KMS) to manage encryption keys and Lockbox / attr_encrypted to do the encryption.
@@ -477,37 +477,9 @@
```
## Related Projects
To securely search encrypted data, check out [Blind Index](https://github.com/ankane/blind_index).
-
-## Upgrading
-
-### 1.0
-
-KMS Encrypted 1.0 brings a number of improvements. Here are a few breaking changes to be aware of:
-
-- There’s now a default encryption context with the model name and id
-- ActiveSupport notifications were changed from `generate_data_key` and `decrypt_data_key` to `encrypt` and `decrypt`
-- AWS KMS uses the `Encrypt` operation instead of `GenerateDataKey`
-
-If you didn’t previously use encryption context, add the `upgrade_context` option to your models:
-
-```ruby
-class User < ApplicationRecord
- has_kms_key upgrade_context: true
-end
-```
-
-Then run:
-
-```ruby
-User.where("encrypted_kms_key NOT LIKE 'v1:%'").find_each do |user|
- user.rotate_kms_key!
-end
-```
-
-And remove the `upgrade_context` option.
## History
View the [changelog](CHANGELOG.md)