-
Notifications
You must be signed in to change notification settings - Fork 24.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
docs: use valid settings in examples #92651
docs: use valid settings in examples #92651
Conversation
Logstash Central Management allows key/value map for pipeline settings, but the Elasticsearch API does not perform validation of the provided settings. Here, we remove from our examples settings that have no semantic meaning to Logstash, and replace them with a meaningful key/value pair
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Logstash Central Management allows key/value map for pipeline settings, but the Elasticsearch API does not perform validation of the provided settings. Here, we remove from our examples settings that have no semantic meaning to Logstash, and replace them with a meaningful key/value pair
@grcevski can this be auto-backported to 7.17 too since the source of the doc bug goes back to 7.12? I'm not a regular contributor to Elasticsearch, so I'm not sure what the protocol is. |
Hi @yaauie, since we already merged this PR we can't really use the auto backport and merge option anymore. We'll need a separate PR on the 7.17 branch. You don't need another approval for backports, just force merge the PR when it comes out green from tests. I'm happy to look over the backport PR as well, just tag me. When making the backport PR, just follow what the automation did here for the 8.6 branch #92654, prefix in the title, referencing the original PR inside Thanks for fixing this. |
Logstash Central Management allows key/value map for pipeline settings, but the Elasticsearch API does not perform validation of the provided settings. Here, we remove from our examples settings that have no semantic meaning to Logstash, and replace them with a meaningful key/value pair
Logstash Central Management allows key/value map for
pipeline_settings
, but the Elasticsearch API does not perform validation of the provided settings.Here, we remove from our examples introduced in #67788 settings that have no semantic meaning to Logstash, and replace them with a key/value pair
"queue.max_bytes": "1gb"
that has been valid since at least Logstash 6.0,