Add Bulk Import file download & decompression services
What does this MR do?
This MR adds file download & decompression services that are going to be used during group import process when using Group Migration tool (https://docs.gitlab.com/ee/user/group/import/).
A .ndjson.gz
file is going to be downloaded from a recently added 'group relations export API' (https://docs.gitlab.com/ee/api/group_relations_export.html) in order to import its contents into a group. In order to achieve this, we need to be able to safely download and decompress mentioned files.
File download service performs several validations:
- Do a
HEAD
request to/export_relations/download
endpoint to validate it's content-length & content-type headers. Make sure they are acceptable. - Start downloading a file by streaming its contents. If during download process file size exceeds the limit - raise exception and remove the file.
File decompression service:
- Decompresses a
.gz
file (similar to what we do in Import/Export but withouttar
) - Performs decompressed file size validation to make sure that decompressed file size is within limits.
Both services are not yet used in this MR and are going to be used in the future MR (next one in #329864 (closed) series).
Mentions #329864 (closed)
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team