Skip to content

Draft: Spike secret manager using AR encryption

Albert requested to merge spike-secret-manager-rails-encryption into master

What does this MR do and why?

Create Secret model with encrypted attributes:

:value - encrypted using attr_encrypted gem with per_attribute_iv and aes-256-gcm :active_record_encryption_value - encrypted using AR encryption with default key provider

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports