diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-05-12 15:08:59 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-05-12 15:08:59 +0000 |
commit | 0024c2f44455cf5ace9235a7efa195c12a1d72d2 (patch) | |
tree | 72d2e7d8f03fd479b8b3ca9915d12d116d37948f /doc/development/integrations/secure.md | |
parent | cb3b9f9243555b0c26145e2992a9f01f7fa47bf5 (diff) | |
download | gitlab-ce-0024c2f44455cf5ace9235a7efa195c12a1d72d2.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/integrations/secure.md')
-rw-r--r-- | doc/development/integrations/secure.md | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/doc/development/integrations/secure.md b/doc/development/integrations/secure.md index cc7daccfa5b..0f4fa1a97a8 100644 --- a/doc/development/integrations/secure.md +++ b/doc/development/integrations/secure.md @@ -290,9 +290,6 @@ useful when debugging. The default value for `SECURE_LOG_LEVEL` should be set to `info`. When executing command lines, scanners should use the `debug` level to log the command line and its output. -For instance, the [bundler-audit](https://gitlab.com/gitlab-org/security-products/analyzers/bundler-audit) scanner -uses the `debug` level to log the command line `bundle audit check --quiet`, -and what `bundle audit` writes to the standard output. If the command line fails, then it should be logged with the `error` log level; this makes it possible to debug the problem without having to change the log level to `debug` and rerun the scanning job. |