Category and subcategory for inputs

[grotlue]

• API for categories and subcategories (for a specific category)
• Input can store one category
• Input can store 1+ subcategories of that category

[grotlue]

We will need an API for categories and subcategories (for a specific category). This will also be needed for the Data Source wizard.

[AntonEbel]

These are the

• cats subcats
• plus "generic" subcat

[grotlue]

For this cycle adding categories and subcategories in the UI is out of scope.

[patrickmann]

Illuminate packs will include the data required by the input setup wizard. Specifically, the following fields:

• category: the category name, as it will be shown in the UI
• subcategories: list of all associated subcategory names
• subcategory_descriptions: list of descriptions, corresponding to subcategories list
• input_types: list of all associated input types

[grotlue]

Will it also include information regarding associated licenses?

[patrickmann]

@grotlue Yes - Illuminate pack includes editions, which tells us if it is available in open/enterprise/security and cloud/on-prem. E.g.: https://github.com/Graylog2/graylog-project-illuminate/blob/develop/_meta/packs/bind_dns.toml We can make that available via the new categories API.

[tellistone]

We should add an “other” category. If user selects this, we present them with all (valid) illuminate packs.

[patrickmann]

Obsolete, since Illuminate is providing the required APIs