-
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
update elastic-agent-libs to v0.9.11 #39765
Conversation
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
d6781d3
to
b20cb10
Compare
Converting into draft until elastic/elastic-agent-libs#209 gets merged and I can update this PR to use v0.9.10 |
b20cb10
to
9286ac9
Compare
I found another issue, back to draft until elastic/elastic-agent-libs#210 gets merged |
Update elastic-agent-libs to v0.9.9 and add tests to ensure Beats always logs as JSON to a file when no logging is explicitly configured.
9286ac9
to
d9dacd1
Compare
Update elastic-agent-libs to v0.9.11 and add tests to ensure Beats always logs as JSON to a file when no logging is explicitly configured. An integration test is added to assert the behaviour.
Proposed commit message
Update elastic-agent-libs to v0.9.11 and add tests to ensure Beats always logs as JSON to a file when no logging is explicitly configured.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
None, it's a bug fix.
## Author's ChecklistHow to test this PR locally
You can also run the integration test added:
If you want to see the test failing before the fix, downgrade
elastic-agent-libs
Then run the testt
## Related issues## Use cases## Screenshots## Logs