Skip to content

Resolve "[2] [Backoffice] Moteur de recherche à simplifier"

Rémi PAILHAREY requested to merge 12-2-backoffice-moteur-de-recherche-a-simplifier into dev

What does this MR do and why?

🗑 Remove Meilisearch 🎉

Impacts :

  • Less Openshift deployments configs
  • Simplified search engine : now all consent search go to MySQL database
  • Soft-deleted consents will always be displayed
  • Updated tests for searching consents

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally (or on alpha)

  • Checkout to branch in client and server projects
  • In server, run docker build . -t backoffice-server
  • In client, run yarn local-up
  • With Postman create a dozen of consents, delete some of them
  • Connect to the backoffice in your browser and go to consents page
  • Try to do some searches, select some consents, export them... You should see all consents, even those whe were softly-deleted

MR acceptance checklist

To be completed by the chosen reviewer.

Quality

  • Confirmed
  1. For the code that this change impacts, I believe that the automated tests validate functionality that is highly important to users. If the existing automated tests do not cover this functionality, I have added the necessary additional tests or I have added an issue to describe the automation testing gap and linked it to this MR.
  2. I have made sure that the sonar quality coverage is up to standards.
  3. I have considered the impact of this change on the front-end, back-end, and database portions of the system where appropriate and applied.
  4. I have tested this MR in all supported browsers or determined that this testing is not needed.
  5. I have confirmed that this change is backwards compatible across updates (migrate up needs a migrate down), or I have decided that this does not apply.

Performance, reliability and availability

  • Confirmed
  1. I am confident that this MR does not harm performance, or I have asked a reviewer to help assess the performance impact.
  2. I have considered the scalability risk based on future predicted growth.

Documentation

  • Confirmed
  1. The MR is named after the desired squash commit to feed the changelog linked to the current milestone.
  2. I have added/updated documentation (also updated if the changes feature a deprecation) or I have decided that documentation changes are not needed for this MR.

Security

  • Confirmed
  1. I have confirmed that if this MR does not contains any sensitive informations hidden in the changes.

Deployment

  • Confirmed
  1. When featured on a self-data project release, i have made sure my app version in the manifest and package.json is incremented and any relative changes to the permissions are clearly written and transmitted to Cozy.

Related to #12 (closed)

Edited by Rémi PAILHAREY

Merge request reports