Remove defaults from fields.common.yml for more flexibility #3602
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Having the defaults in code instead of the libbeat fields.yml will allow to reuse the same script also for fields.yml files from a metricbeat module for example without having to merge in the libbeat file. This is a prerequisite for dynamic index template generation in Golang which can be only for a module. The top level `fields` entry was removed as without the defaults, it is not needed anymore. All scripts were adjusted for the new format.
ruflin
force-pushed
the
move-defaults-to-code
branch
from
021acf7 to
d4b74b2
Compare
… with the elasticsearch naming: https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html * Remove object-type from array as arrays cannot be predefined.
ruflin
force-pushed
the
move-defaults-to-code
branch
from
48f82a5 to
1501bd6
Compare
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Having the defaults in code instead of the libbeat fields.yml will allow to reuse the same script also for fields.yml files from a metricbeat module for example without having to merge in the libbeat file. This is a prerequisite for dynamic index template generation in Golang which can be only for a module.
The top level
fieldsentry was removed as without the defaults, it is not needed anymore.All scripts were adjusted for the new format.