@Gerard Conway 2
Thank you for providing the details about the issue you're experiencing. I understand that the increased number of parameters might be confusing. Let me address each of your concerns:
OrchestratorRequired Parameters:
The required parameters for configuring the Orchestrator container largely depend on the specific Large Language Model (LLM) and vector data store being utilized, which are. controlled by the plugin parameters
MODEL_PLUGIN_ENTRY_POINT
RETRIEVER_PLUGIN_ENTRY_POINT
The LANGCHAIN_... parameters are optional and are used to enable Langsmith. You can set the LANGCHAIN_TRACING_V2="false" and leave the other parameters blank if you don't want to use Langsmith
VECTOR_DB_TOKEN is indeed used for authentication purposes. If your Milvus setup does not require authentication, you can leave this parameter blank. The system should handle it gracefully. If authentication is enabled, this should be set to username:password.
Running a Test Query Against the Orchestrator REST Endpoint:
The endpoint is provided just to test very basic functionality. The documentation for each parameter can be seen by looking at the request schema in the swagger documentation.
To execute a simple test against the Orchestrator and make sure it is functional, you need to set the following parameters in your request body:
{
"user_intent": "UserIntent",
"prompt": "How to create a bar chart?"
}
I hope this clarifies your questions. If you have any further doubts or need assistance with any specific configuration, feel free to reach out. We're here to help you get everything running smoothly.
Regards,
Marcelo Gallardo