Skip to content
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

[7.7] Allow a wider range of characters for logstash.log.pipeline_id (#17243) #17357

Merged
merged 2 commits into from
Mar 31, 2020
Merged

[7.7] Allow a wider range of characters for logstash.log.pipeline_id (#17243) #17357

merged 2 commits into from
Mar 31, 2020

Conversation

ycombinator
Copy link
Contributor

Backports the following commits to 7.7:

* Allow a wider range of characters for logstash.log.pipeline_id

Allow a wider range of characters for `logstash.log.pipeline_id`.
The `NOTSPACE` should be fine, but for covering any case, `DATA` would be safer.
Should solve #17242

* update tests for logstash plain 7.4 pipeline id

* Failed tests

* update changelog
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@ycombinator ycombinator merged commit cdc6abf into elastic:7.7 Mar 31, 2020
@ycombinator ycombinator deleted the backport/7.7/pr-17243 branch March 31, 2020 13:26
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…lastic#17243) (elastic#17357)

* Allow a wider range of characters for logstash.log.pipeline_id (elastic#17243)

* Allow a wider range of characters for logstash.log.pipeline_id

Allow a wider range of characters for `logstash.log.pipeline_id`.
The `NOTSPACE` should be fine, but for covering any case, `DATA` would be safer.
Should solve elastic#17242

* update tests for logstash plain 7.4 pipeline id

* Failed tests

* update changelog

* CHANGELOG grooming

Co-authored-by: Luca Belluccini <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants