Workaround the dashboards' reliance on types #4218
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kibana still relies on types, and works around it by setting
index.mapping.single_type=false
when creating the
.kibana
index. If the Beats dashboards are inserted before this indexis created, however, the import will fail. This adds
single_type=false
when creating the.kibana
index.This is a temporary solution until Kibana removes types from its usage and we have an API
to index the dashboards.
This was inspired by elastic/kibana#11451 and should fix our failing integration tests.