-
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
Add new shipper
output type
#31281
Add new shipper
output type
#31281
Conversation
This will allow us to start experimenting with the new shipper architecture.
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
This reverts commit 16ef370.
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
/test |
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
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.
Please do not expose backoff
settings and convert the documentation page to a README.md file.
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, but see @kvch's comment about not exposing the backoff settings.
@belimawr I addressed all comments including the one about the backoff configuration. I planned to re-request reviews after the CI passed. |
/test |
1 similar comment
/test |
/test |
I have strange failures in the e2e tests, I'm pretty sure my added feature should not break anything existing:
@cmacknz would you mind if I merged it regardless the failures? |
Some of the failing E2E tests (https://beats-ci.elastic.co/job/e2e-tests/job/e2e-testing-mbp/job/main/876/testReport/) are listed as flaky: https://github.com/elastic/e2e-testing/issues The packaging step is being triggered because of the changes to go.mod here. |
The exact same test set is failing on main so I don't think they are caused by your change: https://beats-ci.elastic.co/job/e2e-tests/job/e2e-testing-mbp/job/main/876/#showFailuresLink |
I think it is safe to merge this given your change didn't introduce the E2E test failures. |
This will allow us to start experimenting with the new shipper architecture.
What does this PR do?
This will allow us to start experimenting with the new shipper architecture.
Checklist
- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.THERE ARE NO TESTS WHATSOEVER
The tests for the actual gRPC communication will be added later.
Closes elastic/elastic-agent-shipper#22