gitlab-org--gitlab-foss/app/services/users
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
..
activity_service.rb Fix typo in user activity debug log message 2017-06-03 23:11:53 -07:00
build_service.rb current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00
create_service.rb Fire system hooks when a user is created via LDAP or OAuth 2017-08-25 22:00:07 -07:00
destroy_service.rb Make sure repository's removal work for legacy and hashed storages 2017-08-22 06:33:20 +02:00
migrate_to_ghost_user_service.rb Use Ghost user when edited_by, merged_by deleted 2017-07-19 11:35:17 +02:00
refresh_authorized_projects_service.rb Reduce wait timings for Sidekiq jobs 2017-06-19 16:14:07 +02:00
update_service.rb Fire system hooks when a user is created via LDAP or OAuth 2017-08-25 22:00:07 -07:00