-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Fleet] Fix bug caused by API changes #120886
Conversation
Pinging @elastic/fleet (Team:Fleet) |
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.
Can we update the API integration test for this?
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
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.
🚀
* fix endpoint integration * added test
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
* fix endpoint integration * added test
* fix endpoint integration * added test
Summary
Fixed bug caused by API changes in #119494
Steps to reproduce:
Expected with this fix: Endpoint page opens as expected without error
Root cause:
Made
/epm/packages/pkgkey
route deprecated returningresponse
field, and instead using/epm/packages/pkgName/pkgVersion
returningitem
field from UI.In some cases,
pkgVersion
is not specified (optional path param), and in this case, router calls the deprecated API.To fix this, I'm returning
item
field from deprecated API as well. This makes it easier to remove the deprecated API later, since the UI is already using the newitem
field.After fix:
Checklist