Commit graph

8 commits

Author SHA1 Message Date
Sean McGivern
5883ce95ef current_application_settings belongs on Gitlab::CurrentSettings
The initializers including this were doing so at the top level, so every object
loaded after them had a `current_application_settings` method. However, if
someone had rack-attack enabled (which was loaded before these initializers), it
would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
have that method.

To fix this:

1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
   `Object.new.current_application_settings` to work.
2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
   like that in several places.
3. Change the initializers to use that new form.
2017-08-31 13:38:33 +01:00
Douwe Maan
6e1b52b8b9 Merge branch 'rs-filter-authentication_token' into 'security'
Add authentication_token to filter_parameters list

See merge request !2041
2016-12-08 21:23:09 -03:00
Jacob Vosmaer
437bebb0ff Don't send Private-Token headers to Sentry
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/22537
2016-10-04 16:57:01 +02:00
Stan Hu
0fe4cf2b0f Fix Sentry not reporting right program for Sidekiq workers
Moves program tag into the global configuration since this doesn't
change and since Sidekiq workers get a unique context for each event.

Closes #21410
2016-08-25 19:42:52 -07:00
Connor Shea
519a791ef9
Prevent Rails filtered parameters from leaking to Sentry.
As described in their Docs: https://docs.getsentry.com/on-premise/clients/ruby/integrations/rails/
2016-04-28 15:08:23 -06:00
Robert Speicher
6c9ae675b5 Add release tracking for Sentry 2016-02-17 14:05:58 -05:00
Jeroen Nijhof
7a609858f0 Use sentry in env production only 2016-01-20 09:48:38 +01:00
Jeroen Nijhof
85e0fce9ee Add sentry integration 2016-01-18 17:15:10 +01:00