ISW - Wizard Step: Select category

[grotlue]

Depends on: #20535

• Two selects, one for the category and one for related subcategory
  • only one category can be selected, but 1+ related subcategories
• User can skip this step
• If an input already has a category and subcategory we apply this to the logic for the first step as follows:
  • and category/subcategory has related Illuminate packs -> https://github.com/Graylog2/graylog-plugin-enterprise/issues/8872
  • and category/subcategory does not have related Illuminate packs -> ISW - Wizard Step: Input Diagnostics #20683

Next step:

• If category and cubcategory selected
  • selection valid for illuminate content? -> https://github.com/Graylog2/graylog-plugin-enterprise/issues/8872
  • selection not valid for illuminate content ? -> ISW - Wizard Step: Input Diagnostics #20683
• If category and subcategory not selected -> ISW - Wizard Step: Input Diagnostics #20683

Dependencies:

• Checking illuminate validity depends on API for category and subcategory illuminate check #20684

[tellistone]

For this cycle: we might not have the cat/sub dataset in place in time.

We can hardcode the Category (we already know all the categories). optional to set

For subcat, we can just allow one option for now (generic), which is equivalent of null. optional to set.

We don't need to show associated input here, so just a generic tickbox UI where user needs to select 1+ items

[tellistone]

• Gray out subcategories which are for license types the cluster lacks license for.

• New subcategories should be marked with a “New!”. We can ascertain this by including an “added” date to the category/subcategory data. We can keep it there when eg. todays date is within 60 days of the date it was added.

[patrickmann]

@tellistone

Gray out subcategories which are for license types the cluster lacks license for.

What are we checking for? If no security license then suppress all subcats that have illuminate?