-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Fallback to bundled packages on GET package route #129999
Conversation
Pinging @elastic/fleet (Team:Fleet) |
29c60d9
to
c97baa3
Compare
c97baa3
to
ea09488
Compare
savedObjectsClient, | ||
pkgName, | ||
pkgVersion, | ||
skipArchive = false, |
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.
This new flag is a pretty ugly hack. I think I'll be able to remove this as part of the work I'm planning for #115032. This is necessary for use cases that depend on the archive having been loaded into the archive cache as a side effect of this function.
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
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
Summary
Fixes #129998
This fixes both the integration detail page and the integration policy editor for cases where the bundled package version is not available in the registry.
Optimizations made in #123509 broke this functionality so I have added an explicit test for this case.
How to test (only valid before 8.2.0 is released)
x-pack/plugins/fleet/target/bundled_packages
/app/integrations/detail/apm-8.2.0/settings
and ensure APM page is shown without errorsChecklist