gitlab-org--gitlab-foss/app/policies
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
..
ci
base_policy.rb current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00
commit_status_policy.rb
deploy_key_policy.rb
deployment_policy.rb
environment_policy.rb
external_issue_policy.rb
global_policy.rb
group_label_policy.rb
group_member_policy.rb
group_policy.rb
issuable_policy.rb
issue_policy.rb
merge_request_policy.rb
namespace_policy.rb
nil_policy.rb
note_policy.rb
personal_snippet_policy.rb
project_label_policy.rb
project_member_policy.rb
project_policy.rb
project_snippet_policy.rb
user_policy.rb