-
Notifications
You must be signed in to change notification settings - Fork 19
[DO NOT REVIEW] [SVLS-8660] test: gitleaks smoke test (DO NOT MERGE) #1142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
litianningdatadog
wants to merge
3
commits into
main
Choose a base branch
from
tianning.li/SVLS-8660-gitleak-test
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
c8ecead
test: gitleaks smoke test — intentional fake credential
litianningdatadog 18d9930
test: use non-allowlisted fake credentials in gitleaks smoke test
litianningdatadog 9bd81b9
test: fix fake AWS key length to exactly 20 chars for gitleaks match
litianningdatadog File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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,21 @@ | ||
| #!/bin/bash | ||
| # SMOKE TEST ONLY — do not merge to main | ||
| # | ||
| # This file exists solely to verify that the gitleaks Secrets Scan CI job | ||
| # correctly blocks PRs containing credential-shaped strings. | ||
| # | ||
| # After confirming the CI job fails on this branch, delete this file and | ||
| # remove this branch. | ||
| # | ||
| # See: .github/workflows/secrets-scan.yml | ||
| # See: PR #1134 test plan — "Optional smoke test" step | ||
|
|
||
| # Fake AWS access key that matches the AKIA[A-Z0-9]{16} pattern. | ||
| # NOT a real credential — generated for smoke-test purposes only. | ||
| # Deliberately avoids the canonical AWS doc examples (AKIAIOSFODNN7EXAMPLE) | ||
| # which are in gitleaks' internal global allowlist and would not be flagged. | ||
| FAKE_AWS_KEY="AKIAT3STFAKEKEY12345" | ||
| FAKE_AWS_SECRET="sM0keT3st+FaKeK3y/ABCDEFGHIJ1234567890ab" | ||
|
|
||
| echo "This file is intentionally flagged by gitleaks for smoke-test purposes." | ||
| echo "Key: $FAKE_AWS_KEY" | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The echo statement on line 20 only prints the AWS key but not the AWS secret. Line 17 defines both
FAKE_AWS_SECRET, but onlyFAKE_AWS_KEYis echoed. For consistency and to verify both credentials are detected by gitleaks, consider also echoing the secret value, or clarify if the secret is only being tested through the variable assignment itself.