Skip to content

Corpus upload modal with graphQL and upload progress

- requested to merge 342433-corpus-upload-progress into master

What does this MR do and why?

This MR is a happy path MR to get part 1 of 2 of corpus upload working. It does not handle all edge cases and error validations.

Follow up issues after this MR:

#342583 (closed)

#342581 (closed)

#342580 (closed)

Notes for reviewer.

Clicking the add button is not covered in the scope of this MR. That is the second part of the 2 part upload. part 1 (this MR) is the upload. The second part is "commit/confirm" the upload which is part of #342580 (closed)

This MR is behind a feature flag, and there are about 4 more issues after this one before we release next milestone, so this MR has happy path only.

Describe in detail what your merge request does and why.

Screenshots or screen recordings

Screen_Shot_2021-11-06_at_5.39.30_PMScreen_Shot_2021-11-06_at_5.41.23_PMScreen_Shot_2021-11-06_at_5.41.30_PMScreen_Shot_2021-11-06_at_5.41.35_PM

How to set up and validate locally

  • From the gitlab repo open a rails console and enable the :corpus_management feature flag
bundle exec rails c

then

[4] pry(main)> Feature.enable(:corpus_management)

Navigate to:

http://172.16.123.1:3000/<group>/<project>/-/security/configuration/corpus_management

Click on New Corpus, upload any zip file of a large size. 500 MB > (or in chrome debugger, throttle network traffic so we can see upload progress)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #342433 (closed)

Edited by -

Merge request reports