A way to disable challenge categories

[MaSven]

I try to get this into our organization environment as a way of learning. But some categories are not relevant for us. So maybe a way of defining categories to disable could help here.

[commjoen]

Hey @MaSven !
thank you so much for wanting to use this!
Just to make sure: What type of categories do you mean? the "focus" types as visible on the main page its challenge table? (https://wrongsecrets.herokuapp.com/) Or do you mean more the environment related type of challenges? (e.g. no "cloud" or no "k8s" or no "vault" challenges)

[MaSven]

The focus types. For example, I want to disable all web3 related challenges.

[commjoen]

That is actually a great idea! But now the question would become: how would you like to be able to configure this for yourself?
What would you prefer?

1. a config file with disabled focus-types as part of the container you release
2. an env-var with disabled focus-types
3. ...anything you can think of? We need to make sure it remains within the context of 1 container as we don't like to force people to locally need to do docer-compose, minikube, etc...

Next: in the UI: is it ok if they are just "disabled" with a notification of being disabled similar to what we now do with unsupported challenges due to lack of a given infrastructure being setup?

[commjoen]

After deciding on this, we will create an issue out of this so we can pick it up for development :) .

[MaSven]

I would prefer the first one. With this, we can provide a forked version of wrongsecrets to the organization for people, who want to run it themselves.

[commjoen]

We created #502 out of this and will eventually pick it up :) .
BTW: Feel free to volunteer on it or if you know anyone who wants to pick it up ^^!

[commjoen]

This feature will be implemented with #1083 .

[commjoen]

The feature has been implemented. Thank you for the idea!