Repository navigation
Release v1.2.0: secret scan allow paths, and links in replies - #13
Conversation
…secret scan secretScan.allowPaths in aisdlc.json holds regular expressions on file paths. GitleaksConfig.psm1 adds them as a second allowlist, and the pre-flight, the C03 gate and Create-GitleaksBaseline.ps1 pass the repository root, so all three skip the same paths. Create-GitleaksBaseline.ps1 now also uses the allowlist of the AI-SDLC. Refs #12
…clone for a baseline A repository widens its own secret scan with secretScan.allowPaths, so each pattern must be anchored, a valid regular expression, free of quotes and control characters, and must not match an ordinary file. A bad pattern stops the scan. The scan prints the paths it skips, so a reviewer sees a wider list in the gate output. Create-GitleaksBaseline.ps1 reads the list from the fresh clone, so the baseline follows what is committed. Refs #12
|
Second commit after a security review: a repository widens its own secret scan with |
# Conflicts: # apm.lock.yaml # core/.apm/skills/ai-sdlc-gates/sync-manifest.json
# Conflicts: # apm.lock.yaml
The scan now only refuses a pattern that would break the generated TOML file or that is not a valid regular expression. Which paths to skip, and how broad, is up to the repository. Refs #12
|
Latest commit: the scan no longer refuses a pattern for being too broad or not anchored. Which paths to skip is up to the repository. It still refuses a pattern with a quote or a control character, or one that is not a valid regular expression, and it still prints the paths it skips. The pull request also holds #14 now, the rule to give the full link to every pull request, issue or page a reply points to. |
Refs #12
Refs #14
What
secretScan.allowPathsinaisdlc.jsonholds regular expressions on file paths that hold secrets on purpose.GitleaksConfig.psm1adds them as a second allowlist, next to the allowlist of the AI-SDLC. Without the field, the config is the same as before.Invoke-Preflight.ps1,Test-GitleaksBaseline.ps1andCreate-GitleaksBaseline.ps1pass the repository root, so all three skip the same paths.Create-GitleaksBaseline.ps1now scans with the generated config, so a new baseline also leaves out the sync manifest hashes.docs/packages/core.mdnames it. Release v1.2.0: CHANGELOG, everyapm.yml, the sync manifest and the lock file.language.mdand in the## Communicationpart ofAGENTS.md. This was pull request Give the full link to every pull request, issue or page a reply points to #15, now closed and folded in here.Checks
GitleaksConfig.Tests.ps1, red before the change and green after, one with a real gitleaks run. The baseline test now expects the generated config, and checks that it is removed.main.