updating to es8 version of a legacy template #1709
Closed
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
|
Summarized some thoughts in #1587 (comment). Let's hold off moving forward with these changes until we're all aligned on what's needed. |
|
No long a requirement, closing |
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.
ECS's 8.0 branch is still generating ES7-style legacy templates (top-level "mappings" and "settings" fields). This updates it to generate ES8-style legacy templates (top-level "template" field with "mappings" and "settings" sub-fields). And there's also a little bit more cleanup for ES version x to legacy in the usage examples.
Addresses #1587 (comment)