Hi ,
I checked with your config.ini , it was able to detect but sonar is unable to detect same aws-secret-access-key in other test.ini file.
Also sonarqube fails to detect aws-secret-access-key in config.ini if length of key is not equal to 40 characters , it does not like greater/less than 40 .
it fails to detect password in config.ini
in logs it says that it analyzed test.ini but in sonarqube UI report ,
it does not flag aws-secret-access-key as vulnerability in test.ini but only in config.ini inspite of having proper sonar.text.inclusions
sonar.text.inclusions=/Users/abcd/Downloads/sonar_poc/test-python/test-sonar/test.ini,config.ini,test.ini,**/*.py,**/*.ini,**/*.properties,**/*.pem
Also sonarqube is unable to detect pem file if pem file has no space between words in “BEGINPRIVATEKEY” and does not check for .pem file extension at all .
Also basis this reply it seems secret detection is not supported in sonar community edition SonarQube Community Build 25.3.0.104237 released - #5 by Lena
23:41:00.639 INFO Analyzing language associated files and files included via "sonar.text.inclusions" that are tracked by git
23:41:00.641 DEBUG 'config.ini' generated metadata with charset 'UTF-8'
23:41:00.642 DEBUG 'sonar-project.properties' generated metadata with charset 'UTF-8'
23:41:00.643 DEBUG 'key.pem' generated metadata with charset 'UTF-8'
23:41:00.643 DEBUG 'test.ini' generated metadata with charset 'UTF-8'
23:41:00.651 INFO 5 source files to be analyzed
23:41:00.668 INFO 5/5 source files have been analyzed