-
Notifications
You must be signed in to change notification settings - Fork 67
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
Add support for searching for packages by asset type #1010
Comments
Now that we have support for subcategories, polluting categories is less of a concern if (for example) a Adding support for filtering on asset type will involve additional UX work as well, so adding a subcategory is a faster path with no dependencies on the Fleet team. |
Thanks for the details about subcategories @jen-huang! I'll relay this to the security folks in our next sync and if sufficient (I imagine so) we can work on adding subcategories to the relevant packages containing security rules. |
Sounds good @spong. For reference, elastic/package-spec#499 is a similar request to add a new subcategory and has details of all the work needed (one liner changes across multiple repos). |
Hey all, this is great enhancement! Question - can an integration belong to a few subcategories? I see that the UEBA subcategory is being added, those also contain rules. cc @jen-huang |
Hi @jen-huang is it possible to for the integration to be in a few different subcategories? Thanks! |
This is an enhancement request for adding support for searching for packages that may contain a specific asset type. Ultimately the goal here is to provide the ability for users to filter integrations within the Fleet UI if they contain a specific asset type.
The use case here for initiating this ER is from a security user that wanted to discover which integrations had
security-rule
assets bundled with them. This is a helpful workflow to security users as it helps enable them to find integrations that they may want to install to provide additional/specific coverage within their Security Solution deployment.Note: Perhaps this could be achieved by leveraging a
Security Rules
category, but not sure if we want to start polluting categories as such, or if that would be a suitable solution in place of further API expansion.cc @TipTip24 @jen-huang
The text was updated successfully, but these errors were encountered: