Make secrets available in the configuration context

Application developers may need to access secrets from within config
files so use before_configuration instead of before_initialize.

Author: jkogara

lib/rails/secrets/railtie.rb

@@ -20,7 +20,7 @@ def secrets=(secrets)
     end
 
     class Railtie < ::Rails::Railtie
-      config.before_initialize do |app|
+      config.before_configuration do |app|
         app.paths.add "config/secrets", with: "config/secrets.yml"
         app.extend(InstanceMethods)
       end

test/dummy/config/environments/development.rb

@@ -26,4 +26,7 @@
   # This option may cause significant delays in view rendering with a large
   # number of complex assets.
   config.assets.debug = true
+
+  # Test whether secrets can be read in a configuration context
+  config.secret_environment_config = Rails.application.secrets.secret_key_base
 end

test/dummy/config/environments/production.rb

@@ -77,4 +77,7 @@
 
   # Use default logging formatter so that PID and timestamp are not suppressed.
   config.log_formatter = ::Logger::Formatter.new
+
+  # Test whether secrets can be read in a configuration context
+  config.secret_environment_config = Rails.application.secrets.secret_key_base
 end

test/dummy/config/environments/test.rb

@@ -33,4 +33,7 @@
 
   # Print deprecation notices to the stderr.
   config.active_support.deprecation = :stderr
+
+  # Test whether secrets can be read in a configuration context
+  config.secret_environment_config = Rails.application.secrets.secret_key_base
 end

test/rails_secrets_test.rb

@@ -8,6 +8,10 @@ class RailsSecretsTest < ActiveSupport::TestCase
     assert_equal "9f4a992", app.secrets.api_token
   end
 
+  test "a config value set in the configuration stage is set to the correct value" do
+    assert_equal app.secrets.secret_key_base, app.config.secret_environment_config
+  end
+
   test "config.secret_key_base is copied from secrets.secret_key_base" do
     assert_equal app.secrets.secret_key_base, app.config.secret_key_base
   end