-
Notifications
You must be signed in to change notification settings - Fork 5k
Cherry-pick #21478 to 7.x: Use new form of fleet API paths #21589
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
Conversation
[Ingest Manager] Use new form of fleet API paths (elastic#21478)
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
jfsiii
left a comment
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.
@nchaulet knows better than I do, but this matches my understanding of the new routes
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures
Steps errors
Expand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
ph
left a comment
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
Cherry-pick of PR #21478 to 7.x branch. Original message:
What does this PR do?
Aligning paths to be even with elastic/kibana#79193
Why is it important?
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.