Document CodeQL alert #3 as a false positive#25
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix code scanning alert(s) flagged in repository
Document CodeQL alert #3 as a false positive
Jul 17, 2026
cephyn
marked this pull request as ready for review
July 17, 2026 12:09
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR addresses code scanning alert #3 (
py/clear-text-logging-sensitive-data). Review of the flagged path showed the alert is not exposing secret material; it matches on a variable name that refers to a Secret Manager identifier, not the secret value.Finding
functions/main.pyflags a log statement that referencesgoogle_search_engine_id_secret_id."GOOGLE_SEARCH_ENGINE_ID"), not the value returned from Secret Manager.Assessment
get_secret(...)infunctions/utils.pyreturns the actual secret payload.search_engine_idand is not logged.Result