Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix config.secret_key_base warning about secrets
Using `config.secret_key_base` currently raises a deprecation warning when used in production because `config.secret_key_base` gets merged into the `secrets` hash instead of being looked up specifically in the `secret_key_base` method. This commit addresses this by not raising a deprecation warning if `secrets.secret_key_base` and `config.secret_key_base` are the same object (meaning `config.secret_key_base` was merged into `secrets). Additionally, an improved deprecation warning is added for apps that continue to set `secret_key_base` in their secrets. The current warning is not great because it isn't directly actionable for users. Currently they will see the warning, not see `secrets` being referenced in their app, and potentially end up confused. The new warning helps users understand the actual change they need to make: not removing a reference to `secrets` but moving `secret_key_base` out of `secrets`.
- Loading branch information