Graylog2
Wizard Step: Select category and subcategory
Depends on: https://github.com/Graylog2/graylog2-server/issues/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
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 ? -> https://github.com/Graylog2/graylog2-server/issues/20683
- If category and subcategory not selected -> https://github.com/Graylog2/graylog2-server/issues/20683
Dependencies:
- Checking illuminate validity depends on https://github.com/Graylog2/graylog2-server/issues/20684
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
-
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.
@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?
@tellistone In the issue we originally defined this:
if selected category does not have related Illuminate packs -> https://github.com/Graylog2/graylog2-server/issues/20683
Is this still the expected behavior? Or do we want to proceed with the non-Illuminate flow?
As discussed today we close this as not planned as this step does not provide value anymore to the wizard as it is today.
