summaryrefslogtreecommitdiff
path: root/spec/initializers
Commit message (Collapse)AuthorAgeFilesLines
* Migrate storage nesting check to GitalyJacob Vosmaer (GitLab)2018-06-271-43/+0
|
* Fix Fog mockingKamil Trzciński2018-06-051-6/+6
|
* Update validatorpresigned-multipart-uploadsKamil Trzciński2018-06-041-3/+4
|
* Support presigned multipart uploadsKamil Trzciński2018-06-042-71/+89
|
* Merge branch 'sh-bump-ruby-2.4' into 'master'Stan Hu2018-06-011-1/+1
|\ | | | | | | | | Upgrade to Ruby 2.4.4 See merge request gitlab-org/gitlab-ce!19055
| * Upgrade to Ruby 2.4.4sh-bump-ruby-2.4Stan Hu2018-05-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Fixes that make this work: * A change in Ruby (https://github.com/ruby/ruby/commit/ce635262f53b760284d56bb1027baebaaec175d1) requires passing in the exact required length for OpenSSL keys and IVs. * Ensure the secrets.yml is generated before any prepended modules are loaded. This is done by renaming the `secret_token.rb` initializer to `01_secret_token.rb`, which is a bit ugly but involves the least impact on other files.
* | Replace grape-route-helpers with our own grape-path-helpersStan Hu2018-05-301-14/+0
|/ | | | | | | | | | | This gem (https://gitlab.com/gitlab-org/grape-path-helpers) makes a number of changes: 1. Brings in @mdelaossa's changes in https://github.com/reprah/grape-route-helpers/pull/21 2. Fixes some broken specs and code for Grape 1.0+ 3. Optimizes the generation of paths by bringing in @dblessing's HashWithIndifferentAccess changes in https://gitlab.com/gitlab-org/gitlab-ce/issues/45718#note_70123793 Closes #45718
* Remove method call to deprecated methodZeger-Jan van de Weg2018-05-111-20/+0
| | | | | Given the settings initializer creates Gitaly Storage Settings objects already, the calls to path can be moved to that initializer.
* Replacing gollum libs for custom gitlab onesFrancisco Javier López2018-04-131-62/+0
|
* Add `direct_upload` setting for artifactsdirect-upload-of-artifactsKamil Trzciński2018-04-051-0/+71
|
* Merge branch '40781-os-to-ce' into 'master'Sean McGivern2018-03-271-0/+24
|\ | | | | | | | | | | | | Bring Object Storage to CE Closes #4171, #4163, #3370, #2841, and #29203 See merge request gitlab-org/gitlab-ce!17358
| * Merge branch '4879-support-private-https-urls-for-object-storage' into 'master'Sean McGivern2018-02-281-0/+24
| | | | | | | | | | | | | | Resolve ""Support private HTTPS urls for object storage"" Closes #4879 See merge request gitlab-org/gitlab-ee!4475
* | Route path lookups through legacy_disk_pathmark-legacy-git-accessJacob Vosmaer2018-03-212-8/+8
|/
* Fix grape-route-helper route shadowinggrape-router-helpers-bugfixMario de la Ossa2018-01-291-0/+14
| | | | | Bringing in https://github.com/reprah/grape-route-helpers/pull/21 as a monkey patch since the grape-route-helpers project seems to be abandoned
* Default to HTTPS for all Gravatar URLsdefault-to-https-for-gravatar-urlsAchilleas Pipinellis2018-01-251-1/+1
| | | | | If using gravatar.com, both plain_url and ssl_url in settings are now served via HTTPS. Make this the default.
* Fixing bug related to wiki last versionFrancisco Javier López2018-01-091-0/+62
|
* Fix rspec errors, and add more tests to MethodCall and ActionViewPawel Chojnacki2017-11-021-4/+1
|
* Read circuitbreaker settings from `Gitlab::CurrentSettings`Bob Van Landuyt2017-10-171-20/+0
| | | | Instead of from the configuration file
* Upgrade doorkeeper-openid_connectMarkus Koller2017-09-201-9/+9
|
* Clean up read_registry scope changesRobin Bobbitt2017-09-181-2/+2
| | | | Closes #37789
* Fix doorkeeper failureKamil Trzciński2017-09-131-1/+1
|
* Setup repositories settings properlymk-setup-settings-properlyMichael Kozono2017-08-171-0/+9
|
* Setup LDAP settings properlyMichael Kozono2017-08-171-0/+16
|
* Add a Circuitbreaker for storage pathsBob Van Landuyt2017-08-042-0/+32
|
* Use described_class when possibleRémy Coutable2017-07-271-20/+20
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Remove superfluous lib: true, type: redis, service: true, models: true, ↵Rémy Coutable2017-07-275-5/+5
| | | | | | services: true, no_db: true, api: true Signed-off-by: Rémy Coutable <remy@rymai.me>
* Instrument Unicorn with Ruby exporterPaweł Chojnacki2017-07-041-1/+9
|
* Instrument MergeRequestDiff#load_commitsinstrument-merge-request-diff-load-commitsSean McGivern2017-06-141-0/+1
| | | | | | | This instrumentation isn't needed strictly for performance measurements, but just to see which controller actions call this method at all. See <https://gitlab.com/gitlab-org/gitlab-ce/issues/30224#note_32306159> for more details.
* Enable Style/Proc cop for rubocopmhasbini2017-04-021-1/+1
|
* Improve storage validation after configuration structure updatestorage-validation-improvementAlejandro Rodríguez2017-03-081-39/+53
| | | | | | | | | | Besides improving the error message to specify what exactly you need to do to solve the error, we now don't skip all storage validations on the test environment, so that you also get a nice error message if you're running tests. Now if conditions are met to skip valitaions (test env or env variable) we still make sure the settings _look_ sane, we just skip verifying the paths exists and meet the given conditions.
* Merge branch '28447-hybrid-repository-storages' into 'master' Sean McGivern2017-03-071-4/+24
|\ | | | | | | | | Update storage settings to allow extra values per shard See merge request !9597
| * Update storage settings to allow extra values per shard28447-hybrid-repository-storagesAlejandro Rodríguez2017-03-031-4/+24
| | | | | | | | | | | | | | This will be necessary when adding gitaly settings. This version doesn't make any functional changes, but allows us to include this breaking change in 9.0 and add the needed extra settings in the future with backwards compatibility
* | Add specs for Doorkeeper resource_owner_authenticatorMarkus Koller2017-03-071-4/+63
| |
* | Only use API scopes for personal access tokensMarkus Koller2017-03-071-0/+12
| |
* | Implement OpenID Connect identity providerMarkus Koller2017-03-071-3/+22
| |
* | Execute metrics initializer earlieretag-notes-pollingAdam Niedzielski2017-03-011-1/+1
|/ | | | | This makes sure that Gitlab::Metrics::RackMiddleware is added before Gitlab::EtagCaching::Middleware.
* Enable Style/SpaceInsideBracketsDouwe Maan2017-02-231-2/+2
|
* Add metric initializer specadd-metrics-initializer-specSean McGivern2017-01-241-0/+16
| | | | | | | | | | An empty file in one of the instrumented directories will cause the app to fail to start when metrics are enabled. Metrics aren't enabled by default in development or test. We could handle the empty file case explicitly, but a file could still not define the constant it is expected to, so instead run the initializer manually in a spec and check that it succeeds.
* Introduce "stub_env" test helper for safely stubbing environment variablesAdam Niedzielski2017-01-091-3/+4
|
* Give priority to environment variablesSean McGivern2016-08-031-6/+68
| | | | | | | | If an environment variable exists for secret_key_base, use that - always. But don't save it to secrets.yml. Also ensure that we never write to secrets.yml if there's a non-blank value there.
* Store all secret keys in secrets.ymlSean McGivern2016-08-031-33/+36
| | | | | Move the last secret from .secret to config/secrets.yml, and delete .secret if it exists.
* Store OTP secret key in secrets.ymlSean McGivern2016-08-031-0/+135
| | | | | | | | | | | | | | | | .secret stores the secret token used for both encrypting login cookies and for encrypting stored OTP secrets. We can't rotate this, because that would invalidate all existing OTP secrets. If the secret token is present in the .secret file or an environment variable, save it as otp_key_base in secrets.yml. Now .secret can be rotated without invalidating OTP secrets. If the secret token isn't present (initial setup), then just generate a separate otp_key_base and save in secrets.yml. Update the docs to reflect that secrets.yml needs to be retained past upgrades, but .secret doesn't.
* Ignore invalid IPs in X-Forwarded-For when trusted proxies are configured.lookatmike2016-07-311-0/+6
|
* Ignore invalid trusted proxies in X-Forwarded-For headerreject-invalid-trusted-proxiesStan Hu2016-07-231-0/+6
| | | | | | | Certain reverse proxies can send invalid IP addresses in the X-Forwarded-For header For example, Apache can send (null). Closes #20194
* Skip repository storage path valitaions on test environmentAlejandro Rodríguez2016-07-211-8/+5
| | | | | Storage path are not created until `TestEnv.init`, so we must skip their validation on initialization.
* Use Pathname to make the repository storage path validations more robustAlejandro Rodríguez2016-07-211-3/+23
|
* Enable Style/EmptyLines cop, remove redundant onesrubocop/enable-cops-for-empty-linesGrzegorz Bizon2016-07-011-2/+0
|
* Merge branch 'rack-request-trusted-proxies' into 'master' Douwe Maan2016-06-301-4/+8
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make Rack::Request use our trusted proxies when filtering IP addresses ## What does this MR do? This allows us to control the trusted proxies while deployed in a private network. ## Are there points in the code the reviewer needs to double check? If we want to limit what is impacted, we can do this specifically for the rack_attack request object. ## Why was this MR needed? Normally Rack::Request will trust all private IPs as trusted proxies, which can cause problems if your users are connection on you network via private IP ranges. Normally in a rails app this is handled by action_dispatch request, but rack_attack is specifically using the Rack::Request object instead. ## What are the relevant issue numbers? Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/17550 ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [ ] ~~[Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)~~ - [ ] ~~API support added~~ - Tests - [x] Added for this feature/bug - [x] All builds are passing - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [ ] Branch has no merge conflicts with `master` (if you do - rebase it please) - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) \cc @stanhu See merge request !4958
| * Make Rack::Request use our trusted proxies when filtering IP addressesrack-request-trusted-proxiesDJ Mountney2016-06-291-4/+8
| | | | | | | | | | | | This allows us to control the trusted proxies while deployed in a private network. Normally Rack::Request will trust all private IPs as trusted proxies, which can caue problems if your users are connection on you network via private IP ranges. Normally in a rails app this is handled by action_dispatch request, but rack_attack is specifically using the Rack::Request object instead.
* | Refactor repository paths handling to allow multiple git mount pointsAlejandro Rodríguez2016-06-291-0/+41
|/