-
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
[Heartbeat] Revert use of wildcard fields #18066
Conversation
Pinging @elastic/uptime (Team:Uptime) |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
|
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.
Looks good.
Jenkins retest |
Jenkins, retest this please |
jenkins run the tests |
jenkins, retest this docker failed |
jenkins run the tests |
In #17687 new x509 fields were added, and the new
wildcard
field type was used. Since wildcard fields have been reverted in Elasticsearch 7.x we should revert them here too, to align the 8.x branch of Heartbeat with the 7.x branch. It wouldn't make sense to have the field mappings go out of alignment with a major version change.The 7.x backport of #17687 has this fix rolled in directly, so no backport is needed.