Implement package pipelines

[jalvz]

The package registry accounts for the possibility of package-level pipelines, that is, not tied to an specific data stream (example).

This is very convenient for APM because most of our pipelines are applicable to all event (data stream) types.
While the spec validates the structure, it seems that Kibana ignores package pipelines completely.

This feature request it to implement the Kibana side.

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[ruflin]

@jalvz Could you open an issue for this in the package-spec as I think this where the discussion needs to start. There are few things that need to be discussed here first.

I think what you are looking for is reusable ingest pipelines, something I think currently fits better into the integrations building process.

The way we handle global assets at the moment is that there we give full flexibility to the package creator and don't care about naming. But if I understand it correctly, here these pipelines are used and required for the data streams to work correctly. Removing / modifying the pipeline would break all the data streams.

[mtojek]

AFAIR Package pipelines are supported now, so resolving.