delta/gitlab/gitlab-ce.git/app/services/auth, branch 44296-commit-path

use Gitlab::UserSettings directly as a singleton instead of including/extending it

2018-02-02T18:39:55+00:00

refactor access handling

2017-10-10T19:15:38+00:00

remove whitespace

2017-10-08T19:01:45+00:00

Issue JWT token with registry:catalog:* scope when requested by GitLab admin

2017-10-08T18:40:01+00:00

`current_application_settings` belongs on `Gitlab::CurrentSettings`

2017-08-31T12:38:33+00:00

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.

Rename user_can_admin? because it's more accurate

2017-08-07T09:29:34+00:00

Also fix the test because we no longer have :empty_project,
just use :project is the same as before

fix typo and check

2017-05-29T19:11:28+00:00

add test and rebase

2017-05-29T19:11:28+00:00

change ability requirement

2017-05-29T19:11:28+00:00

add star for action scope, in order to delete image from registry

2017-05-29T19:11:28+00:00