rails--rails/activerecord/test/models/author_encrypted.rb

# frozen_string_literal: true

require "models/author"

class EncryptedAuthor < Author
  self.table_name = "authors"

  encrypts :name, previous: { deterministic: true }
end

class EncryptedAuthorWithKey < Author
  self.table_name = "authors"

  encrypts :name, key: "some secret key!"
end
Extract encrypted models to their own files We are not encrypting attributes when loading models with the table missing. This way we make sure we only load the encrypted models when necessary during the encryption tests and prevent the problem of missing encrypted attributes due to having cached the class without them encrypted. 2021-03-11 12:46:07 -05:00			`# frozen_string_literal: true`

			`require "models/author"`

			`class EncryptedAuthor < Author`
			`self.table_name = "authors"`

Encourage deterministic encryption to remain unchanged This implements several changes to encourage deterministic encryption to remain unchanged. The main motivation is letting you define unique indexes on deterministically-encrypted columns: - By default, deterministic encryption will always use the oldest encryption scheme to encrypt new data, when there are many. - You can skip this default behavior and make it always use the current encryption scheme with: ```ruby deterministic: { fixed: false } # using this should be a rare need ``` - Deterministic encryption still supports previous encryption schemes normally. So they will be used to add additional values to queries, for example. - You can't rotate deterministic encryption keys anymore. We can add support for that in the future. This makes for reasonable defaults: - People using "deterministic: true" will get unique indexes working out of the box. - The system will encourage keeping deterministic encryption stable: - By always using oldest encryption schemes - By forbidding configuring multiple keys But you can still opt-out of the default if you need to. 2021-03-22 11:02:55 -04:00			`encrypts :name, previous: { deterministic: true }`
			`end`

			`class EncryptedAuthorWithKey < Author`
			`self.table_name = "authors"`

			`encrypts :name, key: "some secret key!"`
Extract encrypted models to their own files We are not encrypting attributes when loading models with the table missing. This way we make sure we only load the encrypted models when necessary during the encryption tests and prevent the problem of missing encrypted attributes due to having cached the class without them encrypted. 2021-03-11 12:46:07 -05:00			`end`