From c579b0ccaad09abd04c9461c843f478b51140a2c Mon Sep 17 00:00:00 2001 From: Paul Osinski Date: Fri, 8 Nov 2024 13:50:21 -0500 Subject: [PATCH] remove unused alert block and add hugo_stats to gitignore --- .gitignore | 1 + docs/content/en/contributing/how-to-write-a-parser.md | 4 ---- docs/content/en/getting_started/running-in-production.md | 2 -- docs/content/en/getting_started/upgrading/_index.md | 3 --- docs/content/en/integrations/parsers/file/aws_scout2.md | 5 +---- docs/content/en/integrations/parsers/file/sarif.md | 4 ---- docs/content/en/usage/features.md | 4 ---- docs/content/en/usage/permissions.md | 2 -- 8 files changed, 2 insertions(+), 23 deletions(-) diff --git a/.gitignore b/.gitignore index 6eab69fb83..3a95a3101f 100644 --- a/.gitignore +++ b/.gitignore @@ -135,3 +135,4 @@ helm/defectdojo/charts docs/public docs/node_modules docs/resources +docs/hugo_stats.json diff --git a/docs/content/en/contributing/how-to-write-a-parser.md b/docs/content/en/contributing/how-to-write-a-parser.md index 71141fcd1b..d008e83647 100644 --- a/docs/content/en/contributing/how-to-write-a-parser.md +++ b/docs/content/en/contributing/how-to-write-a-parser.md @@ -5,9 +5,7 @@ draft: false weight: 1 --- -{{% alert title="Information" color="info" %}} All commands assume that you're located at the root of the django-DefectDojo cloned repo. -{{% /alert %}} ## Pre-requisites @@ -276,9 +274,7 @@ Example for the blackduck hub parser: $ docker-compose exec uwsgi bash -c 'python manage.py test unittests.tools.test_blackduck_csv_parser.TestBlackduckHubParser -v2' {{< /highlight >}} -{{% alert title="Information" color="info" %}} If you want to run all unit tests, simply run `$ docker-compose exec uwsgi bash -c 'python manage.py test unittests -v2'` -{{% /alert %}} ### Endpoint validation diff --git a/docs/content/en/getting_started/running-in-production.md b/docs/content/en/getting_started/running-in-production.md index 6da16d253b..5a17df7ff8 100644 --- a/docs/content/en/getting_started/running-in-production.md +++ b/docs/content/en/getting_started/running-in-production.md @@ -25,9 +25,7 @@ Media files for uploaded files, including threat models and risk acceptance, are ### Instance size -{{% alert title="Information" color="info" %}} Please read the paragraphs below about key processes tweaks. -{{% /alert %}} With a separate database, the minimum recommendations diff --git a/docs/content/en/getting_started/upgrading/_index.md b/docs/content/en/getting_started/upgrading/_index.md index 5a9398a0d8..51e0682577 100644 --- a/docs/content/en/getting_started/upgrading/_index.md +++ b/docs/content/en/getting_started/upgrading/_index.md @@ -13,11 +13,8 @@ should not lose any data. ### Using docker images provided in DockerHub -{{% alert title="Information" color="info" %}} If you\'re using `latest`, then you need to pre pull the `latest` from DockerHub to update. -{{% /alert %}} - The generic upgrade method for docker-compose are as follows: - Pull the latest version diff --git a/docs/content/en/integrations/parsers/file/aws_scout2.md b/docs/content/en/integrations/parsers/file/aws_scout2.md index 2a5cbbf715..d22ec7533b 100644 --- a/docs/content/en/integrations/parsers/file/aws_scout2.md +++ b/docs/content/en/integrations/parsers/file/aws_scout2.md @@ -4,14 +4,11 @@ toc_hide: true --- JS file in scout2-report/inc-awsconfig/aws\_config.js. -{{% alert title="Warning" color="warning" %}} AWS Scout2 Scanner is deprecated and has been replaced with ScoutSuite (https://github.com/nccgroup/ScoutSuite) upstream. Please switch to the new parser for ScoutSuite. -{{% /alert %}} -{{% alert title="Warning" color="warning" %}} This parser is disactivated by default in releases >= 2.3.1 and will be removed in release >= 3.x.x. -{{% /alert %}} + ### Sample Scan Data Sample AWS Scout2 Scanner (deprecated) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/aws_scout2). \ No newline at end of file diff --git a/docs/content/en/integrations/parsers/file/sarif.md b/docs/content/en/integrations/parsers/file/sarif.md index 2b7f2d1009..a6ed9e679c 100644 --- a/docs/content/en/integrations/parsers/file/sarif.md +++ b/docs/content/en/integrations/parsers/file/sarif.md @@ -6,14 +6,10 @@ OASIS Static Analysis Results Interchange Format (SARIF). SARIF is supported by many tools. More details about the format here: -{{% alert title="Information" color="info" %}} SARIF parser customizes the Test_Type with data from the report. For example, a report with `Dockle` as a driver name will produce a Test with a Test_Type named `Dockle Scan (SARIF)` -{{% /alert %}} -{{% alert title="Warning" color="warning" %}} Current implementation is limited and will aggregate all the findings in the SARIF file in one single report. -{{% /alert %}} ##### Support for de-duplication (fingerprinting) diff --git a/docs/content/en/usage/features.md b/docs/content/en/usage/features.md index 474289eb4a..99b760b279 100644 --- a/docs/content/en/usage/features.md +++ b/docs/content/en/usage/features.md @@ -456,11 +456,9 @@ The `SLA_NOTIFY_POST_BREACH` lets you define in days how long you want to be kept notified about findings that have breached the SLA. Passed that number, notifications will cease. -{{% alert title="Warning" color="warning" %}} Be mindful of performance if you choose to have SLA notifications on non-verified findings, especially if you import a lot of findings through CI in \'active\' state. -{{% /alert %}} ### What notification channels for SLA notifications? @@ -492,11 +490,9 @@ modify this schedule to your context. } {{< / highlight >}} -{{% alert title="Information" color="info" %}} The celery containers are the ones concerned with this configuration. If you suspect things are not working as expected, make sure they have the latest version of your settings.py file. -{{% /alert %}} You can of course change this default by modifying that stanza. diff --git a/docs/content/en/usage/permissions.md b/docs/content/en/usage/permissions.md index 512484d51b..52c7857c40 100644 --- a/docs/content/en/usage/permissions.md +++ b/docs/content/en/usage/permissions.md @@ -122,6 +122,4 @@ Many configuration dialogues and API endpoints can be enabled for users or group * Notifications on system level * Configuration permissions for users and groups -{{% alert title="Warning" color="warning" %}} These configuration settings are a powerful tool and should be used with great care. -{{% /alert %}}