-
Notifications
You must be signed in to change notification settings - Fork 118
Closed
Description
When developing locally, we typically don't set ES_API_KEY or ES_USERNAME/ES_PASSWORD for Elasticsearch. However, the current code enforces these authentication parameters as required
.refine(
(data) => {
// Either apiKey is present, or both username and password are present
return !!data.apiKey || (!!data.username && !!data.password);
},
{
message:
"Either ES_API_KEY or both ES_USERNAME and ES_PASSWORD must be provided",
path: ["apiKey", "username", "password"],
}
);Could we make authentication optional for local development environments?
- Simplify local development setup
- Match default Elasticsearch behavior where authentication is not required by default
- Allow developers to quickly test and iterate without configuring auth credentials
Proposed solution
- Make authentication parameters truly optional
Let me know your thoughts on this approach.
Metadata
Metadata
Assignees
Labels
No labels