-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Elastic Agent] Enforce validation on namespace #20693
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
should be done at configuration parse time:
|
@michalpristas Can you confirm that the validation match between Kibana and the Agent? |
i will verify what they are using, we took rules from ES documentation so if they did the same we should be fine. i will confirm |
the validation rules used in kibana is more relaxed I left a comment there in a PR https://github.com/elastic/kibana/pull/75381/files#r476228944 and created issue to align elastic/kibana#75846 |
@michalpristas I think both are incorrect, see my comment in https://github.com/elastic/kibana/pull/75381/files#r476416054 Can you take a lead and synchronize with @jen-huang to have unique validation for both? |
I followed up in elastic/kibana#75846 (comment). |
Closing, fixed by #21406 |
In Kibana we are adding validation on top of the namespace to remove the possibility to create invalid index name.
We should have the same rules applied on the elastic-agent.
The text was updated successfully, but these errors were encountered: