5883ce95ef
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. |
||
---|---|---|
.. | ||
api/helpers | ||
banzai | ||
bitbucket | ||
ci | ||
constraints | ||
container_registry | ||
gitlab | ||
json_web_token | ||
mattermost | ||
microsoft_teams | ||
rspec_flaky | ||
system_check | ||
additional_email_headers_interceptor_spec.rb | ||
after_commit_queue_spec.rb | ||
disable_email_interceptor_spec.rb | ||
event_filter_spec.rb | ||
expand_variables_spec.rb | ||
extracts_path_spec.rb | ||
feature_spec.rb | ||
file_size_validator_spec.rb | ||
gitlab_spec.rb | ||
repository_cache_spec.rb | ||
system_check_spec.rb |