Use data stored in projects instead of ci_projects
- It delegates name, path, gitlab_url, ssh_url_to_repo
- Remove ability to set this parameters using CI API
This fixes GitLab project rename, namespace change, repository rename, etc.
/cc @dzaporozhets
See merge request !1404
- It delegates name, path, gitlab_url, ssh_url_to_repo
- Remove ability to set this parameters using CI API
This fixes GitLab project rename, namespace change, repository rename, etc.
Add support for AWS S3 Server-Side Encryption support
This adds support for AWS S3 SSE with S3 managed keys, this means the
data is encrypted at rest and the encryption is handled transparently to
the end user as well as in the AWS Console.
## Points to double check
I'm unsure on the best way to the handle the default. I've followed the `multipart_upload` de facto in the app. I'm happy to change this if required or if it will impact elsewhere e.g. omnibus packages
I also think I've managed to catch all of the documentation for this change as well.
### Why is this required
Many enterprises require good backup support but also for this to be encrypted. By default backups aren't encrypted, this allows at rest encryption to be supported in GitLab backups providing a layer of security should the physical media not be properly disposed of.
Relates to issue #2478.
See merge request !1280
Documentation of omniauth-ldap limitations
Further documentation about limitations directly impacting settings of
users' LDAP servers.
Closes#2613
See merge request !1421
Improve repo cleanup task
I accidentally wrote a new script, not seeing we already had one.
But the old one did not do enough (it only handled global namespace orhpans) so I figured I should just drop in the new script.
See merge request !1298
This adds support for AWS S3 SSE with S3 managed keys, this means the
data is encrypted at rest and the encryption is handled transparently to
the end user as well as in the AWS Console. This is optional and not
required to make S3 uploads work.
Correct markdown.md docs RE use in commit messages.
This is an improvement to the situation covered in issue #1582. It corrects the markdown documentation to demonstrate that GFM cannot currently be used in commit messages.
See merge request !1343
Add to migration on what to do if you don't want your data.
If you don't want to migrate your CI data , remove the old builds directory.
See merge request !1392
Ci migration doc improvements
Use export improvements in CI 8.0.1, make upgrades a more prominent part of the process, do not shut down GitLab during CI data import.
See merge request !1387
Robert Speicher
Dmitriy Zaporozhets
Dimitar Dimitrov
Kamil Trzcinski
Jacob Vosmaer
Douwe Maan
Sytse Sijbrandij
karen Carias
Cyriac Thomas
Robert Speicher
Paul Beattie
Stan Hu
Robert Schilling
Ben Boeckel
Julio
Chia Yu Pai
Hannes Rosenögger
Job van der Voort
Marin Jankovski
Marin Jankovski