-
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] Identify packages with missing references #128181
Comments
Pinging @elastic/fleet (Team:Fleet) |
I just runned the @hop-dev tools on a branch that throw on reference error and it seems aws was the only one with issue the window package seems to have a mapping error and an analyzer I am wondering if we broke that when moving the mapping. (I created that issue for this problem #128209)
|
This feels like a really useful test for us to have (ensuring all packages can be installed by Kibana), at least at the e2e level. |
Let's track the remaining work in #128493 |
In #127664 it was discovered that some packages contain Saved Objects with missing references to other Saved Objects. In this particular case, we were able to remove the missing reference, but we also updated the package install code to handle objects with missing references by installing them anyways.
In order to make package installation more robust, we should spend some time investigating how many packages contain missing references and determine if this is something we should continue to support or if we should start validating this as part of the package-spec and prevent installations of these packages in the future.
@hop-dev has a neat script for installing all the packages, copied from #127760 (comment):
install_all_packages.js
The text was updated successfully, but these errors were encountered: