Users will want to add their own embeddings (for custom detections, new techniques, etc). The API and command line should allow easy indexing to the database.
This should be really simple.. just init and call the exsiting embedding.VectorDB.add_texts(). But then there will be two chroma clients open when the vectordb scanner is enabled. Idk if this is really even an issue but something to keep in mind.
Now that the vectordb is decoupled from the scanner, this is as simple as adding a new endpoint that calls add_texts. Server can parse config and create a vectordb thats used for this endpoint and the scanner
Users will want to add their own embeddings (for custom detections, new techniques, etc). The API and command line should allow easy indexing to the database.
This should be really simple.. just init and call the exsiting embedding.VectorDB.add_texts(). But then there will be two chroma clients open when the vectordb scanner is enabled. Idk if this is really even an issue but something to keep in mind.