forked from DefectDojo/django-DefectDojo
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update DOCKER.md #398
Open
madchap
wants to merge
73
commits into
master
Choose a base branch
from
madchap-patch-1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update DOCKER.md #398
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fix missing attribute errors * Fix missing references data
Recently we introduced a different on_delete strategy for a JIRA Project configuration. turns out this blocks us from deleting products or engagements which have JIRA Issues attached to their findings. This PR switches back to the previous setting to cascade deletes from products/engagements JIRA Config into the JIRA Issues. Otherwise we would never be able to delete the products/engagements as there is is no easy way for users to remove all the JIRA Issues from the project. Maybe in the future we need a more advanced delete UI making more clear what is being deleted, opt out of certain cascading, etc. We still have the "PROTECT" strategy on JIRA Instance as there it makes sense. We don't want someone to "delete an old jira instance" from DD and mistakenly delete all JIRA Issues created against that instance.
* Set rabbitMQ watermark * bump chart version * proper mappings
* Bandit parser: implement scanner confidence * Fix tests data for integration tests
* implementation before tests * after integration tests * redirect correctly * use setting_enabled instead of custum tag * rename table * redirect and message for product types * refactoring of breadcrumbs * aria-labels for accessibility
…jo#4294) * fix datetime vs date mismatch engagement vs test * fix datetime vs date mismatch engagement vs test
* Contrast parser: switch endpoint to unsaved_endpoints * Remove adding Endpoint everytime * Update unit tests
* Fix internal de-duplicate in Semgrep parser * Add test data * Fix title and some attributes * Fix unit test
* Add parser for CycloneDX * Add more findings for component * Fixes namespace management
Bumps nginx from 1.19.9-alpine to 1.19.10-alpine. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 1.4.8 to 1.4.9. - [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases) - [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/master/CHANGES) - [Commits](https://github.com/sqlalchemy/sqlalchemy/commits) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Add CredScan parser * Fix Flake8 * Add entry in docs Co-authored-by: Maffooch <codymaffucci@Codys-MacBook-Pro-2.local>
* dupe-cascade: refactor * dupe-cascade: refactor: finding.delete() * dupe-cascade: refactor: fix decorator kwargs * dupe-cascade: refactor: fix resfresh from db * dupe-cascade: refactor: add delete tests * harmonize import logic: simplify calculate grade * harmonize import logic: simplify calculate grade * dupe-cascade: refactor: speedup * delete jira issues when product/engagement is deleted * dupe-cascade: refactor: speedup * delete jira issues when product/engagement is deleted * remove comment * dupe-cascade: refactor: add fix loop duplicates * dupe-cascade: refactor: add fix loop duplicates * dupe-cascade: refactor: fix migrations
Bumps [django-extensions](https://github.com/django-extensions/django-extensions) from 3.1.2 to 3.1.3. - [Release notes](https://github.com/django-extensions/django-extensions/releases) - [Changelog](https://github.com/django-extensions/django-extensions/blob/main/CHANGELOG.md) - [Commits](django-extensions/django-extensions@3.1.2...3.1.3) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…efectDojo#4318) Co-authored-by: Renovate Bot <bot@renovateapp.com>
worker and beat have their own entrypoint
Bumps [mysql-connector-python](http://dev.mysql.com/doc/connector-python/en/index.html) from 8.0.23 to 8.0.24. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 1.4.9 to 1.4.10. - [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases) - [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/master/CHANGES) - [Commits](https://github.com/sqlalchemy/sqlalchemy/commits) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ectDojo#4323) * SpotBugs enhancements * added line number to hash_code
Co-authored-by: Maffooch <codymaffucci@Codys-MacBook-Pro-2.local>
…and product type members (DefectDojo#4333)
* jira: fix silent epic error during unit tests * fix tests
* dependency check improvements * dependency check improvements
Release: Merge release into master from: release/1.15.0
As a new DefectDojo user, I was thought I had a corrupt .nessus file, until I renamed it with .xml. This change recognizes XML exports with the `.nessus` extension, matching the documentation at line #245. Also clarifies the error when trying to import a Nessus file.
) This reverts commit b86a921.
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.