Skip to content
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

fix(doc): Breaking Change for HELM deployments with PostgreSQL #10524

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

kiblik
Copy link
Contributor

@kiblik kiblik commented Jul 8, 2024

As #10507 is accepted and merged, it would be good to add upgrade instructions to users.

Copy link

dryrunsecurity bot commented Jul 8, 2024

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security Status Findings
Server-Side Request Forgery Analyzer 0 findings
Configured Codepaths Analyzer 0 findings
IDOR Analyzer 0 findings
Sensitive Files Analyzer 0 findings
SQL Injection Analyzer 0 findings
Authn/Authz Analyzer 0 findings
Secrets Analyzer 0 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective.

Summary:

The code changes in this Pull Request address a breaking change in the HELM deployment of the DefectDojo application, which requires upgrading the PostgreSQL version from 11.x to 12.x or higher. This change is necessary because the previous version of PostgreSQL is incompatible with the Django version 4.2 used in DefectDojo version 3.36.0 and onwards.

In addition to the PostgreSQL version upgrade, the changes also highlight the need for a manual migration process, as PostgreSQL does not support automatic migration of data structures in the filesystem. The provided documentation includes links to various resources that can help with the migration process, such as discussions, Slack conversations, and a blog post.

From an application security perspective, this change is important because it ensures the DefectDojo application is compatible with the latest version of Django, which may include security fixes and improvements. However, the manual migration process may introduce potential security risks if not handled properly. It is crucial to follow the recommended migration steps and ensure the integrity and security of the data during the upgrade process.

Files Changed:

  • docs/content/en/getting_started/upgrading/2.36.md: This file has been updated to document the changes required for upgrading the DefectDojo application from version 2.35.x to 2.36.x. The key changes include the requirement to upgrade PostgreSQL from version 11.x to 12.x or higher, and the need for a manual migration process due to the incompatibility between the previous version of PostgreSQL and the newer version of Django used in DefectDojo 3.36.0 and onwards.

Powered by DryRun Security

@github-actions github-actions bot added the docs label Jul 8, 2024
@kiblik
Copy link
Contributor Author

kiblik commented Jul 8, 2024

@cneill, @mtesauro, @hblankenship, @Maffooch, may I ask for review and acceptance before the release of 2.36.1? There are instructions connected to #10507

Copy link
Contributor

@mtesauro mtesauro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@mtesauro mtesauro merged commit 4c0004c into DefectDojo:bugfix Jul 8, 2024
124 checks passed
@kiblik kiblik deleted the doc_2.36_notes branch July 8, 2024 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants