Opensearch synchronous API

[epipav]

Changes proposed ✍️

What

🤖 Generated by Copilot at ad1640c

This pull request introduces the search-sync-api service, which replaces the search-sync-worker emitter for synchronizing the search index with the database. It adds new workflows, configuration, and scripts for building and deploying the service, and updates the existing services to use the new client. It also simplifies the code and removes unnecessary dependencies and parameters.
​

🤖 Generated by Copilot at ad1640c

We're breaking free from the search-sync-worker
We're using the search-sync-api to unleash the power
We're simplifying the code and removing the waste
We're synchronizing the search with the database

Why

How

🤖 Generated by Copilot at ad1640c

• Add a new utility function to get the search-sync-api client instance, using the configuration from the conf module (link)
• Replace the search-sync-worker emitter with the search-sync-api client in various service files, and remove the tenant id parameter from the trigger methods (link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link,link)
• Add a new property to the default and custom environment variables files that holds the search-sync-api configuration object (link,link)
• Add a new environment variable to the composed, local and test configuration files that specifies the base URL of the search-sync-api service (link,link,link)
• Add a new import statement to the conf index file that imports the search-sync-api configuration interface from the opensearch library, and a new constant that gets the search-sync-api configuration object from the config module (link,link)
• Add a new workflow file that triggers the build and deploy of the search-sync-api service to the LF staging cluster, when there are changes in the relevant paths on the lf-staging branches (link)
• Add a new workflow file that triggers the build and deploy of the search-sync-api service to the staging cluster, when there are changes in the relevant paths on the staging branches (link)
• Add a new input parameter to the production and LF production workflows that allows the user to choose whether to deploy the search-sync-api service or not (link,link)
• Add a new job to the production and LF production workflows that builds and pushes the docker image for the search-sync-api service, if the input parameter is true (link,link)
• Add a new job to the production and LF production workflows that deploys the search-sync-api service to the crowd cluster, if the input parameter is true (link,link)
• Add a new script file that defines the dockerfile, context and repository for the search-sync-api service image (link)
• Add a new dockerfile for the search-sync-api service that copies the relevant files and installs the dependencies (link)

Checklist ✅

• Label appropriately with Feature, Improvement, or Bug.
• Add screenshots to the PR description for relevant FE changes
• New backend functionality has been unit-tested.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.