-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove MySQL and RabbitMQ #10661
Remove MySQL and RabbitMQ #10661
Conversation
DryRun Security SummaryThe pull request includes a wide range of updates to the DefectDojo application's infrastructure, focusing on improving the development, testing, and deployment processes, while ensuring security best practices are followed. Expand for full summarySummary: The code changes in this pull request cover a wide range of updates to the DefectDojo application's infrastructure, including GitHub workflows, Docker Compose configurations, and various utility scripts. The changes are primarily focused on improving the application's development, testing, and deployment processes, with a focus on simplifying the configuration, optimizing the test environments, and aligning with the latest Docker Compose functionality. From an application security perspective, the changes do not introduce any obvious security concerns. The updates appear to be well-designed and follow security best practices, such as the removal of unnecessary dependencies, the use of environment variables for configuration, and the implementation of robust error handling and input validation. However, it's important to review the entire codebase and configuration to ensure that there are no potential security vulnerabilities or misconfigurations that could be introduced. Files Changed:
Code AnalysisWe ran Riskiness🟢 Risk threshold not exceeded. |
Converting to draft until I get to the bottom of rest test framework failures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I note that there is a comment from gitbot regarding the following:
Check warning on line 461 in helm/defectdojo/values.yaml
GitHub Actions
/ Lint chart
461:12 [truthy] truthy value should be one of [false, true]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments on this one, and a couple files that weren't totally purged of MySQL/RabbitMQ references yet:
- We can yank these lines ignoring MySQL/RabbitMQ out of
renovate.json
now - This gory bit of
dojo/metrics/utils.py
- This bit in settings.dist.py
- The mysqlclient blob in NOTICE
There are some other comments about MySQL-specific behavior scattered in some other files but we can worry about that later - I don't think it will hurt anything to leave them alone for now.
Co-authored-by: Charles Neill <[email protected]>
Co-authored-by: Charles Neill <[email protected]>
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Co-authored-by: Charles Neill <[email protected]>
Co-authored-by: Charles Neill <[email protected]>
Co-authored-by: Charles Neill <[email protected]>
Co-authored-by: Charles Neill <[email protected]>
I would really rather not touch these to be honest 😅 @cneill |
No problem, just thought I'd mention them since ~everything else is cleaned up and we might forget about them. But we're probably already doing enough with this PR. |
Conflicts have been resolved. A maintainer will review the pull request shortly. |
Quality Gate passedIssues Measures |
Following the deprecation of MySQL and RabbitMQ (see discussion post here), it is now time for removal. The following places have been touched:
--profile
flag from other tests usingdc-
helper scripts[sc-7056]