| Age | Commit message (Collapse) | Author |
|---|
|
Migrate GitlabProject (re)move project endpoints
Closes gitaly#873
See merge request gitlab-org/gitlab-ce!16249
|
|
Closes #41739
|
|
This reverts commit 8040edcce8b4e736b4f4857e6709f94aeb5e274c.
|
|
This reverts commit a2cb92495c3149b69eb734596e80fbdd54b0b2dc.
|
|
|
|
|
|
Migration is done through a small refactoring, which makes us call
endpoins which are performing the same actions for namespaces.
Tests are added to ensure only the project is removed that should be
removed.
Closes gitlab-org/gitaly#873
|
|
|
|
Fix changes dropdown ellipsis working across browsers
Closes #41561 and #41684
See merge request gitlab-org/gitlab-ce!16281
|
|
|
|
Closes #41561
|
|
Backport authorized_keys
Closes gitlab-ee#3953
See merge request gitlab-org/gitlab-ce!16014
|
|
list in the board
|
|
Backport "Fix environment scope regex" to CE
Closes gitlab-ee#4308
See merge request gitlab-org/gitlab-ce!15945
|
|
This will enable admins to identify who actually made the API request.
Relates to #36960
|
|
|
|
'master'
Resolve "Timeout is not set for gitaly fetch_remote calls"
Closes #41683
See merge request gitlab-org/gitlab-ce!16245
|
|
|
|
The spec for "#add_key does nothing" would always have passed,
since the expectation was on both the wrong object and message.
|
|
|
|
|
|
Originally from branch 'fix-authorized-keys-enabled-default-2738' via merge request https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2240
Removed background migrations which were intended to fix state after using Gitlab
without a default having been set
Squashed commits:
Locally, if Spring was not restarted, `current_application_settings` was still cached, which prevented the migration from editing the file. This will also ensure that any app server somehow hitting old cache data will properly default this setting regardless.
Retroactively fix migration
This allows us to identify customers who ran the broken migration. Their `authorized_keys_enabled` column does not have a default at this point.
We will fix the column after we fix the `authorized_keys` file.
Fix authorized_keys file if needed
Add default to authorized_keys_enabled setting
Reminder: The original migration was fixed retroactively a few commits ago, so people who did not ever run GitLab 9.3.0 already have a column that defaults to true and disallows nulls. I have tested on PostgreSQL and MySQL that it is safe to run this migration regardless.
Affected customers who did run 9.3.0 are the ones who need this migration to fix the authorized_keys_enabled column.
The reason for the retroactive fix plus this migration is that it allows us to run a migration in between to fix the authorized_keys file only for those who ran 9.3.0.
Tweaks to address feedback
Extract work into background migration
Move batch-add-logic to background migration
Do the work synchronously to avoid multiple workers attempting to add batches of keys at the same time.
Also, make the delete portion wait until after adding is done.
Do read and delete work in background migration
Fix Rubocop offenses
Add changelog entry
Inform the user of actions taken or not taken
Prevent unnecessary `select`s and `remove_key`s
Add logs for action taken
Fix optimization
Reuse `Gitlab::ShellAdapter`
Guarantee the earliest key
Fix migration spec for MySQL
|
|
Originally branch 'mk-toggle-writing-to-auth-keys-1631'
See merge request !2004
Squashed commits:
Add authorized_keys_enabled to Application Settings
Ensure default settings are exposed in UI
Without this change, `authorized_keys_enabled` is unchecked when it is nil, even if it should be checked by default.
Add “Speed up SSH operations” documentation
Clarify the reasons for disabling writes
Add "How to go back" section
Tweak copy
Update Application Setting screenshot
|
|
Add find key by base64 key or fingerprint to the internal API
See merge request !250
Squashed changes:
Add unique index to fingerprint
Add new index to schema
Add internal api to get ssh key by fingerprint
Change API endpoint to authorized_keys
Add InsecureKeyFingerprint that calculates the fingerprint without shelling out
Add require for gitlab key fingerprint
Remove uniqueness of fingerprint index
Remove unique option from migration
Fix spec style in fingerprint test
Fix rubocop complain
Extract insecure key fingerprint to separate file
Change migration to support building index concurrently
Remove those hideous tabs
|
|
Make tasklist:changed test in merge_request_spec.js async
Closes #34649
See merge request gitlab-org/gitlab-ce!16097
|
|
Resolve "Fix wrong output protocol pattern when adding custom domain to Pages"
Closes #28260
See merge request gitlab-org/gitlab-ce!16279
|
|
'40418-migrate-existing-data-from-kubernetesservice-to-clusters-platforms-kubernetes' into 'master'
Migrate existing data from KubernetesService to Clusters::Platforms::Kubernetes
Closes #40418
See merge request gitlab-org/gitlab-ce!15589
|
|
Run background migrations with a minimum interval
Closes #41624
See merge request gitlab-org/gitlab-ce!16230
|
|
|
|
Resolve "No Rendering of emoji's in Group-Overview after update"
Closes #40549
See merge request gitlab-org/gitlab-ce!16098
|
|
Remove the Commit#tree method
See merge request gitlab-org/gitlab-ce!16236
|
|
Incorporate RemoteService.FetchInternalRemote Gitaly RPC
Closes gitaly#857
See merge request gitlab-org/gitlab-ce!16140
|
|
Move invites spinach test to Rspec
See merge request gitlab-org/gitlab-ce!16126
|
|
Move explore groups spinach test to RSpec
See merge request gitlab-org/gitlab-ce!16129
|
|
|
|
|
|
into 'master'
Protected branch is now created for default branch on import
Closes #3968
See merge request gitlab-org/gitlab-ce!16198
|
|
|
|
|
|
|
|
|
|
|
|
|
|
kubernetes_service_without_template
|
|
|
|
|
|
|
|
|
|
|
|
|
