Open lomky opened 3 months ago
I think there's a second strategic point here, which is to make a new environment for sandbox that duplicates production, so we can have a different key file. I'll commit to dealing with this shortly.
I'm shocked this is the first time I've done this on this project, but I accidentally pushed straight to main instead of a branch, ha. The commit setting up the ability to use a staging environment is in https://github.com/DARIAEngineering/dcaf_case_management/commit/f70d63400a291f2f9bbb8349021a1e6178063243 and I'll move our actual staging environment to use that later. Should be a noop more generally.
Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.
What are we trying to do?
Right now we use the (quite old) style secrets file. Let's move over to using the new-style
configs/credentials/
filesWhat feature or behavior is this required for?
Keeping up with Rails Norms
After a bit of research, let's follow the per-env key migration route. That best matches our current setup.
This article has a good step by step.
Development & Test
development.key
&test.key
Rails.application.secrets
withRails.application.credentials
Production
Either @colinxfleming or @lomky should handle this.
production.key
Final cleanup
delete the old secrets file
Anything else?
S/o to the work done in #3128 & #3220 for kicking this off!