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.

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

Update IngestPipeline Const to ingest_pipeline #581

Merged
merged 1 commit into from
Jul 2, 2020

Conversation

ruflin
Copy link
Member

@ruflin ruflin commented Jul 2, 2020

This went missing during the update to the new ingest pipeline paths.

For now, all the ingest pipelines are copied to two directories and will be cleaned up later when Kibana is ready.

This went missing during the update to the new ingest pipeline paths.

For now, all the ingest pipelines are copied to two directories and will be cleaned up later when Kibana is ready.
@ruflin ruflin requested a review from mtojek July 2, 2020 12:55
@ruflin ruflin self-assigned this Jul 2, 2020
ruflin added a commit to ruflin/integrations that referenced this pull request Jul 2, 2020
For now, both exist. As soon as Kibana is updated, the old one can be removed.

This PR is only in draft yet, as it also requires the registry to be updated to elastic/package-registry#581 first.
@ruflin ruflin merged commit 41c150c into elastic:master Jul 2, 2020
@ruflin ruflin deleted the rename-ingest-pipeline-dir branch July 2, 2020 13:29
ruflin added a commit to elastic/integrations that referenced this pull request Jul 2, 2020
For now, both exist. As soon as Kibana is updated, the old one can be removed.

This PR is only in draft yet, as it also requires the registry to be updated to elastic/package-registry#581 first.
eyalkraft pushed a commit to build-security/integrations that referenced this pull request Mar 30, 2022
For now, both exist. As soon as Kibana is updated, the old one can be removed.

This PR is only in draft yet, as it also requires the registry to be updated to elastic/package-registry#581 first.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants