[Fleet] Adding ML module asset type#94950
Conversation
|
Pinging @elastic/fleet (Feature:Fleet) |
|
Pinging @elastic/ml-ui (:ml) |
|
@elasticmachine merge upstream |
|
It would be good to have a test that installs and removes a package with an ml module to make sure it works as expected. @skh might be able to give some guidance here on how to do this best? |
#88189 is the PR where we added the |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
ruflin
left a comment
There was a problem hiding this comment.
LGTM. @jgowdyelastic Would be good to follow up with an ml module in the integration packages so we can test this in real world.
@EricDavisX Would be nice if this could also be tested manually like install / remove as soon as we have it in a package.
@jen-huang Could you have one more look to make sure this looks as it should?
|
@ruflin thank you. |
💚 Build SucceededMetrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
|
Great to hear @jgowdyelastic . @EricDavisX I think that means you can remove it from your list, sorry for the noise. Lets get the PR merged then! |
* [Fleet] Adding ML module asset type * adding test * guessing asset ids * better guess at IDs * renaming asset ids Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [Fleet] Adding ML module asset type * adding test * guessing asset ids * better guess at IDs * renaming asset ids Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: James Gowdy <jgowdy@elastic.co>
| { id: '47758dc2-979d-5fbe-a2bd-9eded68a5a43', type: 'epm-packages-assets' }, | ||
| { id: '318959c9-997b-5a14-b328-9fc7355b4b74', type: 'epm-packages-assets' }, | ||
| { id: 'e21b59b5-eb76-5ab0-bef2-1c8e379e6197', type: 'epm-packages-assets' }, | ||
| { id: '4c758d70-ecf1-56b3-b704-6d8374841b34', type: 'epm-packages-assets' }, |
There was a problem hiding this comment.
hey @jgowdyelastic, I'm working on a similar PR #95885 for security_rule assets. how'd you get these UUIDs? I looked through your commits and couldn't reverse engineer your process
There was a problem hiding this comment.
@rw-access It took me quite a while to work this out, after adding lots of log statements in fleet I found the best way is to run the tests locally and then copy the IDs out of the errors.
They need to be in the correct order, which again I determined from the test errors.
I'm happy to help if this doesn't work for you.
You need to follow the steps here to run the tests:
https://github.com/elastic/kibana/blob/master/x-pack/plugins/fleet/README.md#tests
Adds support for ML module asset type.
Related to elastic/package-spec#152