Closed (fixed)
Project:
Search API Typesense
Version:
1.0.x-dev
Component:
Code
Priority:
Major
Category:
Feature request
Assigned:
Reporter:
Created:
4 Feb 2025 at 14:06 UTC
Updated:
17 Jul 2025 at 16:59 UTC
Jump to comment: Most recent
Problem/Motivation
It seems this module requires its own standalone Typesense cluster. I cannot use this module with a Typesense cluster that is shared by other unrelated sites.
Proposed resolution
Is it possible to use this module with a Typesense cluster that is shared by other unrelated sites? For example, can I provide this module with a Typesense API key that is limited to specific Typesense collections, such as only those collections that match "acme_.*"?
I understand this would limit/restrict some UI features of this module from working. Is this a possibility? Or is this simply not the intended use-case for this module?
Issue fork search_api_typesense-3504310
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
lussolucaAt the moment, you cannot use the module to point to an existing collection (because the collection is created by Drupal with the information you set in the schema tab).
If a collection with that name doesn't exist on the cluster, I don't see any problem using the module. What issues have you found?
To restrict access, you can create an API key that allows access to only some collections and use that key on the server configuration page.
Comment #3
lussolucaAh, now I got your point!
The module only works if the APi key used is the admin one.
This definitely needs to be addressed; the module must work (with some features disabled) even when configured with a low-permissions API key.
Comment #4
lussolucaComment #7
lussolucaNow, a non-admin key can be used to configure the integration. Of course, the key must have at least access to manage the collection(s) and the documents.