django-DefectDojo
django-DefectDojo copied to clipboard
Estimated remediation date
This PR adds a new field to the Finding model to store the Planned Remediation Date. This is used to track progress towards remediation and to indicate to security teams that the Finding is being triaged. This is useful to organizations without Jira.
Closing while I read more on migrations
I am still trying to figure out the best way to get the migration file from the container to version control. I don't expect this PR will be completed, but am looking for feedback on the change and the approach.
@37b If you are using the dev
environment, then the working directory is bind mounted. Once you make the migrations from the uwsgi container, it will also be created on the host machine and be in version control.
For this PR though, there is a few extra fields in the migration that I am not sure how they made it into. Beyond that, and some of the formatting changes, the PR looks good overall!
@37b If you are using the
dev
environment, then the working directory is bind mounted. Once you make the migrations from the uwsgi container, it will also be created on the host machine and be in version control.For this PR though, there is a few extra fields in the migration that I am not sure how they made it into. Beyond that, and some of the formatting changes, the PR looks good overall!
@cody-m-tibco
Thanks for the info. I was having trouble running locally and knew it was related to the M1 Mac (ARM) but didn't have time to look into a fix. It was pretty simple - just needed to add profile: linux/amd64
to the compose file. I'll redo the migrations and fix failing tests.
@cody-m-tibco Are some of these tests broken overall? I can't get them to pass using a clean dev
branch
@37b I looked at each of the failing tests and it is the same test at each level that is failing. It is when creating a finding manually. I image selenium is getting hung up on the extra field on the page. You can run the tests manually by following this guide
I also recommend commenting out this line to see where the hang up is directly on the page
@Maffooch Thanks for your help with the tests - I am still getting my bearings with Django development.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
@37b targeting next release for getting this merged. Thank you for your PR!
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
@StefanFl @Maffooch Finally got this going, can you give it another look?
Looks okay to me after the compose file is removed from the commit
@StefanFl what do you think?