delta/gitlab/gitlab-ce.git/spec/features/admin, branch performance-bar-sql gitlab.com: gitlab-org/gitlab-ce.git Read circuitbreaker settings from `Gitlab::CurrentSettings` 2017-10-17T09:50:32+00:00 Bob Van Landuyt bob@vanlanduyt.co 2017-10-12T12:13:59+00:00 619021fd7a6ac68e2821f89f746fea3a72c25e3b Instead of from the configuration file 
Instead of from the configuration file
Replaces `tag: true` into `:tag` in the specs 2017-10-07T11:57:54+00:00 Jacopo beschi.jacopo@gmail.com 2017-10-03T08:35:01+00:00 0ce6785851510ccb49f0d1edc0220aca46f815f5 Replaces all the explicit include metadata syntax in the specs (tag: true) into the implicit one (:tag). Added a cop to prevent future errors and handle autocorrection. 
Replaces all the explicit include metadata syntax in the specs (tag:
true) into the implicit one (:tag).
Added a cop to prevent future errors and handle autocorrection.
Merge branch 'fly-out-top-level-item' into 'master' 2017-09-07T13:26:48+00:00 Filipa Lacerda filipa@gitlab.com 2017-09-07T13:26:48+00:00 b8adc0d0423ac53bf94aeb4361c3eb82a4e905c6 Add top level items to fly-out navigation Closes #36294 See merge request !13981 
Add top level items to fly-out navigation

Closes #36294

See merge request !13981
 Merge branch 'tc-test-admin-log-links' into 'master' 2017-09-06T15:56:12+00:00 Dmitriy Zaporozhets dmitriy.zaporozhets@gmail.com 2017-09-06T15:56:12+00:00 8a2aab447a6d5bb540d3c514f6aac41f5e47ee29 Put Admin loggers in before_action for easier overriding in EE See merge request !14081 
Put Admin loggers in before_action for easier overriding in EE

See merge request !14081
 Add top level items to fly-out navigation 2017-09-06T13:54:17+00:00 Phil Hughes me@iamphill.com 2017-09-01T07:41:31+00:00 c56100b3ec26a0f5d71bb80f94c661674b3226b8 This only appears when in the collapsed sidebar. If the sidebar is expanded, then these items are hidden & no fly-out navigation is displayed. Closes #36294 
This only appears when in the collapsed sidebar. If the sidebar is expanded, then these items are hidden & no fly-out navigation is displayed.

Closes #36294
Put loggers in before_action for easier overriding in EE 2017-09-06T13:25:51+00:00 Toon Claes toon@iotcl.com 2017-09-06T13:05:35+00:00 ddf892b9f26138c0fd43bbfa3b5d602ed954f59b Make it easier to override the set of loggers, by putting them in a separate method. Also modify spec so it tests for links, instead of checking for regular text. 
Make it easier to override the set of loggers, by putting them in a
separate method.

Also modify spec so it tests for links, instead of checking for
regular text.
Merge branch '17849-allow-admin-to-restrict-min-key-length-and-techno' into 'master' 2017-09-01T19:23:08+00:00 Robert Speicher robert@gitlab.com 2017-09-01T19:23:08+00:00 223849fa173b7059e717ba4f9c02075a452cbd49 Add settings for minimum key strength and allowed key type Closes #17849 See merge request !13712 
Add settings for minimum key strength and allowed key type

Closes #17849

See merge request !13712
 Rework the permissions model for SSH key restrictions 2017-08-30T19:50:44+00:00 Nick Thomas nick@gitlab.com 2017-08-25T13:08:48+00:00 6847060266792471c9c14518a5106e0f622cd6c5 `allowed_key_types` is removed and the `minimum_<type>_bits` fields are renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies that the key type is disabled. This also feeds through to the UI - checkboxes per key type are out, inline selection of "forbidden" and "allowed" (i.e., no restrictions) are in. As with the previous model, unknown key types are disallowed, even if the underlying ssh daemon happens to support them. The defaults have also been changed from the lowest known bit size to "no restriction". So if someone does happen to have a 768-bit RSA key, it will continue to work on upgrade, at least until the administrator restricts them. 
`allowed_key_types` is removed and the `minimum_<type>_bits` fields are
renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies
that the key type is disabled.

This also feeds through to the UI - checkboxes per key type are out, inline
selection of "forbidden" and "allowed" (i.e., no restrictions) are in.

As with the previous model, unknown key types are disallowed, even if the
underlying ssh daemon happens to support them. The defaults have also been
changed from the lowest known bit size to "no restriction". So if someone
does happen to have a 768-bit RSA key, it will continue to work on upgrade, at
least until the administrator restricts them.
Add settings for minimum key strength and allowed key type 2017-08-30T19:50:44+00:00 Nick Thomas nick@gitlab.com 2017-08-21T10:30:03+00:00 b0f982fbdf69c292ab4530c0aaaf1ab42f4e7a01 This is an amalgamation of: * Cory Hinshaw: Initial implementation !5552 * Rémy Coutable: Updates !9350 * Nick Thomas: Resolve conflicts and add ED25519 support !13712 
This is an amalgamation of:

* Cory Hinshaw: Initial implementation !5552
* Rémy Coutable: Updates !9350
* Nick Thomas: Resolve conflicts and add ED25519 support !13712
fixed up a bunch of specs 2017-08-29T14:35:49+00:00 Phil Hughes me@iamphill.com 2017-08-14T14:11:31+00:00 669fb299c71806fc8bee8b13a4600982e3fff623 some caused by webkit prefixes 
some caused by webkit prefixes