Test Types: Return support for disabling test types via the active flag#10562
Test Types: Return support for disabling test types via the active flag#10562Maffooch merged 2 commits intoDefectDojo:bugfixfrom
active flag#10562Conversation
DryRun Security SummaryThe pull request focuses on improving the handling of inactive test types in the Expand for full summarySummary: The code changes in this pull request focus on improving the handling of inactive test types in the
From an application security perspective, these changes are a positive improvement as they enhance the overall maintainability and reliability of the application. By properly handling and excluding inactive test types, the application can prevent potential issues or confusion that could arise from including outdated or irrelevant functionality. Additionally, the changes to the Files Changed:
Code AnalysisWe ran Riskiness🟢 Risk threshold not exceeded. |
|
I'm not 100% sure, this will work in multi-Django deployment (k8s, number of pods |
|
That is a good point. Maybe it really would be better to totally move away from the "in memory" list of parsers. I'll see what I can do |
Return the ability to remove a given test type from being used, but without deleting the test type. This change has the following impacts for test types with a False
activestatus:There is a slight caveat to this such that the API swagger schema does not appear to be calling the function to generate the list of test types each time the schema is loaded. The test type list is updated on uwsgi reload. My best guess is the schema is being cached on the server somehow.
[sc-6869]