Closed bestickley closed 4 months ago
My testing, with a different string in .gitallowed
indicated that the file IS being utilized.
I will try again with a couple of other regular expressions to see if this can be narrowed down.
@bestickley - would you please try the following regexp in place of the one you had specified?
.*[0-9]{12}.*
That one seemed to work for me.
Also, I noticed that on the Ubuntu image that is being used, the expressions .*\d{12}.*
and .*[0-9]{12}.*
produce different results when used with grep -E
. The latter finds/matches 12-digit strings on a line, the former does not.
@climbertjh2, you're a genius, that worked! Thank you very much.
When I add the following .gitallowed in the root of my repo:
and run
git secrets --scan
locally (not in ash) with aws patterns registered I get no errors. BUT, when I commit file and run ash then I get error:From the
du
command above in aggregated_results.txt, I know that .gitallowed is making it's way into ash.Please help. Thank you!