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

Copy ingest-pipeline to ingest_pipeline #153

Merged
merged 2 commits into from
Jul 2, 2020

Conversation

ruflin
Copy link
Member

@ruflin ruflin commented Jul 2, 2020

For now, both exist. As soon as Kibana is updated, the old one can be removed.

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 marked this pull request as ready for review July 2, 2020 13:33
@ruflin
Copy link
Member Author

ruflin commented Jul 2, 2020

PR updated as elastic/package-registry#581 was merged.

@mtojek
Copy link
Contributor

mtojek commented Jul 2, 2020

I think we need to inform @jonathan-buttner about such changes.

@ruflin
Copy link
Member Author

ruflin commented Jul 2, 2020

@mtojek Thanks for the reminder. Yes @jonathan-buttner you also need to update your repo.

@elasticmachine
Copy link

💚 Build Succeeded

Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: [Pull request #153 opened]

  • Start Time: 2020-07-02T13:35:39.299+0000

  • Duration: 3 min 46 sec

@ruflin ruflin merged commit a39d3e1 into elastic:master Jul 2, 2020
@ruflin ruflin deleted the rename-ingest_pipeline branch July 2, 2020 13:39

func main() {
// Find all directories with ingest-pipeline
ingestPipelineDirs, _ := filepath.Glob("./*/dataset/*/elasticsearch/ingest-pi*")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ruflin just noticed this file: I don't think it should be versioned. Is that on purpose?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mtojek No, I forgot to remove it. I also need to take it out on the storage. On the storage layer I thought to keep it in for when I remove the old directories and then directly remove it. We could do the same here or remove it directly.

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.

3 participants