You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was running the bearer scan . --scanner secrets command and realised that there are no links for reference rules (https://docs.bearer.com/reference/rules), community discord and documentation guides(https://docs.bearer.com/guides/bearer-cloud/) present in the html output as in case of terminal output. I'd like to know if there is a need to add these links to maintain uniformity all over the output results.
Expected Behavior
References to be present in the HTML output results to maintain uniformity over scan results.
The HTML output does not link to the docs since the content is basically the same, the other links are not required in this report we just have those in the CLI output.
Gitleaks is actually missing from the docs and had no link to the docs so that will be updated and added in #1521
Description & Reproduction
I was running the
bearer scan . --scanner secrets
command and realised that there are no links for reference rules (https://docs.bearer.com/reference/rules), community discord and documentation guides(https://docs.bearer.com/guides/bearer-cloud/) present in the html output as in case of terminal output. I'd like to know if there is a need to add these links to maintain uniformity all over the output results.Expected Behavior
References to be present in the HTML output results to maintain uniformity over scan results.
Actual Behavior
Possible Fix
Update
secret_detection.yml
file with necessary changes.Your Environment
The text was updated successfully, but these errors were encountered: