-
Notifications
You must be signed in to change notification settings - Fork 444
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
[Google_Workspace] Moving edge processing to ingest pipeline #939
[Google_Workspace] Moving edge processing to ingest pipeline #939
Conversation
Work in progress, adding each fileset once they are completed. |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, left a couple comments that would be nice to have IMO
packages/google_workspace/data_stream/admin/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
packages/google_workspace/data_stream/drive/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
After some discussion, this will be merged for now, as it only runs once every 2 hours, also any additional things we might want to add can be done later, as this is a blocking change. |
…#939) * stashing changes * Moving edge processing from admin fileset to pipelines * adding changelog * updating google_workspace drive fileset from edge processing to ingest pipeline * adding all other filesets, updating and fixing some broken processors, ready for review * renaming all test files to conform to the spec, to pass the elastic-package checks
What does this PR do?
This moves all edge processing to ingest pipelines for the google_workspace package. It also adds some new testdata and pipeline tests.
Checklist
changelog.yml
file.Related issues