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.

Sign up for GitHub

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

Jump to bottom

[EPM] Use component templates for generated mappings #64760

Open
skh opened this issue Apr 29, 2020 · 2 comments
Open

[EPM] Use component templates for generated mappings #64760

skh opened this issue Apr 29, 2020 · 2 comments
Labels
Feature:EPM Fleet team's Elastic Package Manager (aka Integrations) project Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@skh
Copy link
Contributor

skh commented Apr 29, 2020 •
edited
Loading

With alpha 1 (7.8.0), EPM generates index templates v2 from fields.yml files contained in package datasets, but does not use template composition.

This task is to move index template mappings in component templates, and use the composed_of property to use them in index templates.

This is a follow-up issue to #63950

In particular, see #63950 (comment)
@skh skh added Feature:EPM Fleet team's Elastic Package Manager (aka Integrations) project Team:Fleet Team label for Observability Data Collection Fleet team Ingest Management:beta1 labels Apr 29, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Feature:EPM)

@skh skh mentioned this issue Jun 30, 2020
Closed
@ruflin ruflin mentioned this issue Jul 2, 2020
Merged
@ph
Copy link
Contributor

ph commented Oct 16, 2020 •
edited
Loading

I believe this is fixed in #70517 @skh? nevermind, should have read it better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:EPM Fleet team's Elastic Package Manager (aka Integrations) project Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ph @skh @elasticmachine