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

Cherry-pick #15597 to 7.6: Backport Packetbeat TLS: Replace array fields with keyword #15601

Merged
merged 1 commit into from
Jan 15, 2020

Conversation

adriansr
Copy link
Contributor

Use of type: array in some fields (which was inconsistent) causes
those fields to be excluded from the template. This prevents pointing
aliases to those fields, which we need in 7.6+.

Setting those fields to keyword explicitly so that they are included
in the template.

Fixes #15588

Use of `type: array` in some fields (which was inconsistent) causes
those fields to be excluded from the template. This prevents pointing
aliases to those fields, which we need in 7.6+.

Setting those fields to `keyword` explicitly so that they are included
in the template.

Fixes elastic#15588
@adriansr adriansr requested a review from a team as a code owner January 15, 2020 21:53
Comment on lines -624 to -631
- name: tls.server_certificate_chain
type: alias
path: tls.detailed.server_certificate_chain

- name: tls.client_certificate_chain
type: alias
path: tls.detailed.client_certificate_chain

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These aliases need to be removed because it's not possible to point an alias to an object.

@adriansr adriansr merged commit 04a9058 into elastic:7.6 Jan 15, 2020
adriansr added a commit to adriansr/beats that referenced this pull request Jan 16, 2020
Use of `type: array` in some fields (which was inconsistent) causes
those fields to be excluded from the template. This prevents pointing
aliases to those fields, which we need in 7.6+.

Setting those fields to `keyword` explicitly so that they are included
in the template.

Fixes elastic#15588

(cherry picked from commit 04a9058)
adriansr added a commit that referenced this pull request Jan 17, 2020
Use of `type: array` in some fields (which was inconsistent) causes
those fields to be excluded from the template. This prevents pointing
aliases to those fields, which we need in 7.6+.

Setting those fields to `keyword` explicitly so that they are included
in the template.

Fixes #15588

(cherry picked from commit 04a9058)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants