-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* detect-secrets github action * update .secrets.baseline with secrets from ldap-custom-ssl-secret.yaml and openldap-customldif.yaml * run the github action on push only (not pull_request) --------- Co-authored-by: Frederic Mercier <[email protected]>
- Loading branch information
Showing
2 changed files
with
63 additions
and
2 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
name: detect secrets | ||
|
||
on: push | ||
|
||
# A workflow run is made up of one or more jobs that can run sequentially or in parallel | ||
jobs: | ||
# This workflow contains a single job called "detect-secrets" | ||
detect-secrets: | ||
runs-on: ubuntu-latest | ||
|
||
# Steps represent a sequence of tasks that will be executed as part of the job | ||
steps: | ||
|
||
# Checks-out your repository under ${{github.workspace}}, so your job can access it | ||
- uses: actions/checkout@v4 | ||
|
||
- name: scan all the files (not just the ones committed), generate a report, and check that there are no actual or potential secret | ||
run: | | ||
docker run --pull=always -a stdout \ | ||
-v ${{github.workspace}}:/code \ | ||
--entrypoint /bin/sh \ | ||
icr.io/git-defenders/detect-secrets:0.13.1.ibm.61.dss-redhat-ubi \ | ||
-c "detect-secrets --version; | ||
detect-secrets scan --all-files --exclude-files "^.git/.*" --update .secrets.baseline; | ||
detect-secrets audit --report --fail-on-unaudited --fail-on-live --fail-on-audited-real .secrets.baseline" |
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