[Fleet] Add threat_intel category#135758
Conversation
|
Pinging @elastic/fleet (Team:Fleet) |
|
@elasticmachine merge upstream |
mtojek
left a comment
There was a problem hiding this comment.
Maybe we should drop all package category labels from Kibana and leave package-less ones only? EPR should be the only source of truth here.
|
@mtojek I didn't unravel the logic too closely, but from what I saw the UI is displaying the ones from the registry whenever possible. The hardcoded ones are part of fallback logic related to registering custom integrations. |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💛 Build succeeded, but was flakyFailed CI StepsTest Failures
Metrics [docs]Public APIs missing comments
Page load bundle
History
To update your PR or re-run it, just comment with: cc @jen-huang |
Summary
Resolves #135525. This PR adds code to support typing of a new category,
threat_intel. This is mostly for code consistency, functionally the PR does not do anything besides allow custom integrations to be registered to the new category.It is not expected for the UI to display this category yet until a real package using it is served from the registry.