update go mod elatic/beats reference with newer commit #970
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michel-laterman
added
enhancement
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
michel-laterman
force-pushed
the
update-beats-mod
branch
from
3955f2a to
297ace7
Compare
michel-laterman
force-pushed
the
update-beats-mod
branch
from
41e91b6 to
213e9bf
Compare
|
I've created #971 to track updating the module properly once |
|
was able to do an end to end test on my machine with 8.0. I had to add the |
mergify bot
pushed a commit
that referenced
this pull request
Dec 10, 2021
* update go mod elatic/beats reference with newer commit * Add license overrides * Fix broken integration test * Use libbeat BuildServerConfig (cherry picked from commit 7706e2b)
mergify bot
added a commit
that referenced
this pull request
Dec 10, 2021
* update go mod elatic/beats reference with newer commit * Add license overrides * Fix broken integration test * Use libbeat BuildServerConfig (cherry picked from commit 7706e2b) Co-authored-by: Michel Laterman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the problem this PR solves?
Update the version of elastic/beats to from
v7.11.1to a more recent one. Specifically elastic/beats@4641f75 off the8.0branch.How does this PR solve the problem?
Updated module includes libbeat support
ssl.ca_trusted_fingerprint(elastic/beats#29229). This option is used by libbeat to trust a self-signed CA when bootstrapping a secure by default cluster in 8.0.The fleet-server will use this option when connecting to ES.
How to test this PR locally
The elastic-agent modifications to support/pass this option to fleet-server can be found with: elastic/beats#29128.
Create a snapshot build of the agent, and fleet-server.
start an 8.0+ ES node and Kibana
go to Kibana and setup fleet (ensure that the elasticsearch scheme is
https.enroll the fleet server with the command and the
--fleet-server-es-ca-trusted-fingerprintflag, using thesha256fingerprint that elasticsearch outputs on startup. i.e.:Related issues