BUG: `Trying {candidate_service_account}` gets logged directly instead of candidate_service_account

[peb-peb]

Affected Component

• [ ] Crawl
• [ ] CredsDB
• [x] Scanner
• [ ] Test
• [ ] Docs
• [ ] Python
• [ ] GCP APIs

Describe the bug

During Scanning resources with latest codebase, I got the following output at the end:

2023-03-15 11:49:28 - INFO - Retrieving credentials from /home/peb/Downloads/sa_keys/qwiklabs-gcp-02-f08fbae4db62-d34106e8dd27.json
...
...
2023-03-15 11:52:14 - INFO - Retrieving cloud source repositories qwiklabs-gcp-02-fa95c3a79f7c
2023-03-15 11:52:17 - INFO - Trying {candidate_service_account}
2023-03-15 11:52:17 - INFO - Trying {candidate_service_account}
2023-03-15 11:52:17 - INFO - Trying {candidate_service_account}
2023-03-15 11:52:17 - INFO - Trying {candidate_service_account}
2023-03-15 11:52:17 - INFO - Trying {candidate_service_account}
2023-03-15 11:52:17 - INFO - Trying {candidate_service_account}
2023-03-15 11:52:17 - INFO - Trying {candidate_service_account}
2023-03-15 11:52:17 - INFO - Trying {candidate_service_account}
2023-03-15 11:52:17 - INFO - Trying {candidate_service_account}
2023-03-15 11:52:17 - INFO - Saving results for qwiklabs-gcp-02-fa95c3a79f7c into the file

To Reproduce

Steps to reproduce the behavior:

3. Run the command gcp-scanner -o output -k /home/peb/Downloads/sa_keys -l INFO

Expected behavior

2023-03-15 12:03:27 - INFO - Trying qwiklabs-gcp-02-fa95c3a79f7c@qwiklabs-gcp-02-fa95c3a79f7c.iam.gserviceaccount.com should be logged

Current behavior

Trying {candidate_service_account} gets logged

Screenshots