Provide parity in the rake tasks for projects using Zoekt-based code search

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Rake tasks are used to control GitLab Advanced Search and retrieve the related information. When we migrate the code search to Zoekt, we need a similar parity.

Proposal

Update the rake tasks to support Zoekt based Code search.

For the first iteration, I would suggest we will have the following tasks to support Zoekt,

• Create, delete recreate Zoekt index

  • gitlab-rake gitlab:zoekt:create_empty_index
  • gitlab-rake gitlab:zoekt:delete_index
  • gitlab-rake gitlab:zoekt:recreate_index
  • gitlab-rake gitlab:zoekt:index

• Indexing control to allow pausing and resuming indexing

  • gitlab-rake gitlab:zoekt:pause_indexing
  • gitlab-rake gitlab:zoekt:resume_indexing

• Clear index status in database

  • gitlab-rake gitlab:zoekt:clear_index_status

• Show users the indexing information

  • gitlab-rake gitlab:zoekt:info

Some examples

• GitLab Elastic info-style Rake task for admins to get general information about the Zoekt deployment
• Could also include output from the above rake task in SOS output; useful for support use cases