[EPM] Install Lens assets from packages if present. #88189
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Implements #85428
This adds the kibana asset type 'lens' to the supported asset types.
How to test this manually
You need a package that contains a Kibana asset of type
lens
.I have a modified version of the apache package that can be used with a local registry (ping me on slack), or wait for elastic/integrations#530 to be available in the staging registryThe packageapache-0.3.1
in the staging registry has one (thanks @mtojek for providing the package!).Navigate to the package in Fleet->Integration. On the integration detail page, verify that the Lens asset is listed on the right side:
Install the package with the "Install Apache assets" on the Settings tab (or any other way). The installation should go through without errors.
After installation, verify in "Visualize" that a Lens asset has been installed and appears in the list of visualizations (for me it's on the third page and called "Workers with Lens", this might be different with the new
apache-0.3.1
package from elastic/integrations#530 ):Checklist