[7.17 backport] Update elastic-agent-client used in 7.17 releases
Proposed commit message
Update the elastic-agent-client to the latest tagged release. Update protobuf libraries. elastic-agent will have v2 related functions disabled.
Checklist
- [x] My code follows the style guidelines of this project
- [x] I have commented my code, particularly in hard-to-understand areas
- ~~I have made corresponding changes to the documentation~~
- ~~I have made corresponding change to the default configuration files~~
- [ ] I have added tests that prove my fix is effective or that my feature works
- ~~I have added an entry in
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.~~
:green_heart: Build Succeeded
the below badges are clickable and redirect to their specific view in the CI or DOCS
![]()
![]()
![]()
![]()
![]()
Expand to view the summary
Build stats
-
Start Time: 2024-05-06T15:36:13.833+0000
-
Duration: 138 min 56 sec
Test stats :test_tube:
| Test | Results |
|---|---|
| Failed | 0 |
| Passed | 20613 |
| Skipped | 1423 |
| Total | 22036 |
:green_heart: Flaky test report
Tests succeeded.
:robot: GitHub comments
Expand to view the GitHub comments
To re-run your PR in the CI, just comment with:
-
/test: Re-trigger the build. -
/package: Generate the packages and run the E2E tests. -
/beats-tester: Run the installation tests with beats-tester. -
runelasticsearch-ci/docs: Re-trigger the docs validation. (use unformatted text in the comment!)
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)
To double check, Fleet server was confirmed to bootstrap with these changes?
Yes, last time i tested it bootstrapped locally correctly. We can also try to make a custom issue and check on ESS as well.