More verbose logging for deprecated path access

Current logging tells us we've isolated the calls to about 5 call sites, now we'd like to know what is calling these methods.

More verbose logging for deprecated path access
aad2e06f · Zeger-Jan van de Weg · 40683268 · aad2e06f
Unverified Commit aad2e06f authored May 14, 2018 by Zeger-Jan van de Weg
Hide whitespace changes
Inline Side-by-side

Showing with 6 additions and 2 deletions

deprecations.rb config/initializers/deprecations.rb +6 -2

No files found.
--- a/config/initializers/deprecations.rb
+++ b/config/initializers/deprecations.rb
-deprecator = ActiveSupport::Deprecation.new('11.0', 'GitLab')
-
 if Gitlab.dev_env_or_com?
+  deprecator = ActiveSupport::Deprecation.new('11.0', 'GitLab')
+
+  deprecator.behavior = -> (message, callstack) {
+    Rails.logger.warn("#{message}: #{callstack[1..20].join}")
+  }
+
  ActiveSupport::Deprecation.deprecate_methods(Gitlab::GitalyClient::StorageSettings, :legacy_disk_path, deprecator: deprecator)
 end