CORE-4385

.github/CODEOWNERS

@@ -0,0 +1 @@
+/.github/*  @bombbomb/Dev-Admins

.github/workflows/ripsecrets.yaml

@@ -0,0 +1,22 @@
+name: RipSecrets
+on: [pull_request]
+jobs:
+  ripsecrets:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: Download ripsecrets
+        run: |
+          wget https://static.bombbomb.com/ci/ripsecrets.tar.gz
+          tar -xzf ripsecrets.tar.gz
+          chmod +x ripsecrets
+          sudo mv ripsecrets /usr/local/bin
+
+      - name: Run ripsecrets
+        run: |
+          ripsecrets `git diff origin/${{ github.base_ref }} --name-only --diff-filter=ACM`

.pre-commit-config.yaml

@@ -0,0 +1,7 @@
+repos:
+-   repo: https://github.com/sirwart/ripsecrets
+    rev: v0.1.5  # Use latest tag on GitHub
+    hooks:
+    -   id: ripsecrets
+        stages: [commit]
+

.secretsignore

@@ -0,0 +1,4 @@
+#full filepaths go here
+
+[secrets]
+#individual secrets go here

README.md

@@ -176,3 +176,10 @@ If the filename ends with `.url` suffix, the content will be processed as an URL
   - description: Set to true to enable pulling of 5XX response content from config map. Used in case if the filename ends with `.url` suffix (Please refer to the `*.url` feature here.)
   - required: false
   - type: boolean
+
+RipSecrets<br><br>
+We implement pipeline secret scanning on all pull request events to prevent credentials from being merged. If the pipeline scanner detects a secret in your changed files it will gate the pull request and you will need to purge the found credential from your code and re-open the PR. To prevent getting gated by this tool and as best practice you should install the secret scanner locally in a pre-commit hook to prevent the secret from ever being committed to the repo in the first place. You can find documentation on how to set it up locally [here](https://bombbomb.atlassian.net/wiki/spaces/CORE/pages/2039775312/Pipeline+Secret+Scanner+Local+Setup)<br>
+Ripsecrets has ways to bypass secret scanning although we should not be ignoring secrets that turn up in the scans. If something is out of your control and blocking the pipeline you can bypass it in one of the following ways<br>
+1. Adding "# pragma: allowlist secret" to the end of the line with the secret.<br>
+2. Adding the specific secret underneath the "[secrets]" block in .secretsignore<br>
+3. Adding the filepath to ignore the whole file aboove the "[secrets]" block in .secretsignore