Restriction of the download of scanner plugins to those that are essentially needed

Hello Pierre, always good to get prompt feedback. Thank you for that.

I skimmed through the jira ticket and would like to offer you one more scenario that would benefit from bespoken configurability of plugin usage:

  • Say there is something which makes a used plugin behave erratic (say, a bug in UTF-8 parsing :innocent: ).
    • Reproducibly erratic
    • 100s of jobs failing erratic

So the goal of this is probably more than impact on performance. It [c|w]ould also increase resilience.

Being able to firefight said scenario globally as an instance admin might be beneficial … but actually, while writing all this, i am pondering about “something, something, quality gate” :thinking: :cold_face:

So: Implementationwise: good luck! :smiley: :+1: If you like, keep us updated about the reasoning behind your (e.g. the teams) chosen implementation :wink: