Temporary Multiple Search Endpoints for Testing in Finesse Backend

[k-allagbe]

Currently, our backend only searches through the Azure index. We can also search in our PostgreSQL database and look up static files. To better evaluate these options, we should setup different endpoints for each search type. This is a temporary measure for testing, as we plan to eventually choose and stick with one main search source.

Task

Create a unique endpoint in our backend for each search type: one for Azure, one for PostgreSQL, and one for static files. By doing this, we can easily test each method by simply using the relevant endpoint.

Acceptance Criteria

• Separate, working endpoints for Azure, PostgreSQL, and static files.
• Each endpoint returns accurate search results.
• Frontend can switch between these endpoints without any hassle.
• Provide clear guidelines on using each endpoint.
• Conduct tests to ensure each endpoint functions correctly.

It’s important to note that this multi-endpoint setup is for testing purposes only. Once we evaluate the performance and effectiveness of each source, we'll decide on the best one to use long-term for our backend searches.

[k-allagbe]

This has already been done in separate issues #1, #2 and #3. Closing this.