-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
x-pack/packetbeat: install Npcap at start-up when required #29112
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
785cbf3
to
cf07d80
Compare
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
8bb5150
to
bb4394f
Compare
E2E failure looks unrelated. |
/test |
This pull request is now in conflicts. Could you fix it? 🙏
|
a1e8d80
to
32d89dd
Compare
I have disentangled and rolled back the license additions to add in a non-technical PR (to come). |
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.
Nice work
/test |
As far as I see the |
Yes that's expected. The image is the same, but the installer asset is only copied to the build tree in the x-pack builds. It can be made to only be used in the x-pack build at the cost of some code duplication. |
This reverts commit 1e7c68e.
This add automated installation of an OEM Npcap provided by embedding in the packetbeat executable. The installation is configurable to allow users to retain their own version of Npcap if they have one and to specify the location of the install. To simplify support this configurablity will not be included in the next release, but is comitted here to allow it to be reverted back out to make it easier to add if the decision is made to do that later. (cherry picked from commit 72a43be) # Conflicts: # go.mod
…9112) This add automated installation of an OEM Npcap provided by embedding in the packetbeat executable. The installation is configurable to allow users to retain their own version of Npcap if they have one and to specify the location of the install. To simplify support this configurablity will not be included in the next release, but is comitted here to allow it to be reverted back out to make it easier to add if the decision is made to do that later.
…k-version-after-8-0-creation * upstream/master: (69 commits) Update stale config following (elastic#30082) Make include_matches backwards compatible with 7.x config (elastic#30032) [Filebeat] Update handling of elasticsearch server logs (elastic#30018) Remove SSL3 support from libbeat and its documentation. (elastic#30071) Revert "Packaging: rename arm64 suffix to aarch64 in the tar.gz artifacts ONLY (elastic#28813)" (elastic#30083) [libbeat] Add script processor to all beats (elastic#29752) Add fonts to support more different types of characters for multiple languages (elastic#29861) libbeat/reader: Fix messge conversion to beat.Event (elastic#30057) probot[stale]: ignore issues with the tag flaky-test (elastic#30065) [DOCS] Add redirect for GSuite module (elastic#30034) [Automation] Update elastic stack version to 8.1.0-aa69d697 for testing (elastic#30012) Remove msitools install for windows build, using the latest docker image with msitools preinstalled (elastic#30040) filebeat/generator/fields: fix dropped error (elastic#29943) Include the error message with auditd module events (elastic#30009) [Metricbeat] gcp: add firestore metricset (elastic#29918) probot: update stale dates (elastic#29997) Metricbeat enterprise search module: add xpack.enabled support (elastic#29871) x-pack/packetbeat: install Npcap at start-up when required (elastic#29112) [Filebeat] Fix panic in decode_cef when recovering from invalid data (elastic#30038) Correctly fixe how selected packages are defined (elastic#30039) ...
What does this PR do?
This adds hooks to the startup of packetbeat that installs/updates the Elastic OEM-licensed Npcap library.
Why is it important?
See elastic/integrations#2132.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Integration testing depends on infrastructure that does not yet exist so packetbeat integration tests are expected to fail on Windows.Without an embedded artifact x-pack packetbeat now silently continues.Author's Checklist
N/A
How to test this PR locally
Run
go test
in packetbeat/internal/npcap on Windows.Related issues
Use cases
See elastic/integrations#2132.
Screenshots
N/A
Logs
N/A