Better validation of the `pipeline_id`
- Dominant language
- Java
- Stars
- 14.9k
- Forks
- 3.5k
- Avg merge
- 19h 14m
- Merged PRs (30d)
- 63
Description
*Original comment by @ph:*
With the issue LINK REDACTED we have added better validation concerning the uniqueness of the defined values for the config management.
But this is not enough, currently, our `pipeline_id` is not really well defined inside logstash and we are really liberal in the accepted string. We accept anything that can be valid unicode.
With the move to more centralized configuration and multiple pipelines we need to make sure that the format for that string is more strict and well defined.
This problem need to be solved inside core, but I've created this issue to track it in x-pack too.
Original LS issue:https://github.com/elastic/logstash/issues/8164
Contributor guide
Assessment
This issue has not been assessed yet.