How can I identify which GitHub project is using a deprecated Google API

[nikki-05]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

API

Body

I recently received a notification that an older version of a Google API I previously used is being deprecated or disabled. However, I no longer remember which of my GitHub projects is using that API, and I have been unable to identify the affected repository.
How can I search across my GitHub repositories to find the project that is using the deprecated Google API or its credentials? Are there any GitHub search queries, Google Cloud Console logs, API usage reports, or other tools that can help me locate it?
Once I identify the project, what steps should I take to migrate it to the supported API version or safely disable the integration? I want to resolve the issue before the API is disabled and ensure that no project or account-related action is taken because of the outdated integration.

[Pusri27]

Google deprecation emails trigger whenever an active Cloud project registers traffic on older endpoints, so pinpointing the exact project ID and API keys directly from the cloud side will guide you right to the repository in question

What usually happens is that you might have several old test repos or scripts calling that endpoint, and cross referencing your cloud metrics with GitHub code search makes hunting it down super quick

• Check the APIs and Services dashboard across your Google Cloud Console projects to see which specific project is showing recent traffic metrics on the deprecated service
• Look at the Credentials tab in that active project to inspect your API keys and OAuth Client IDs, noting down the key names and the last used timestamps
• Run a global code search across your repositories using GitHub search bar with queries like user:nikki05 "googleapis,com" or targeting the specific API path mentioned in your email
• Search your dependency manifests for legacy SDK client packages with queries like user:nikki05 filename:package,json "@googlecloud" or user:nikki05 filename:requirements,txt "googleapi"
• Once you locate the repository, check the official migration documentation for that service to upgrade your SDK package to the latest client library and update your request structures
• If the repository is an old abandoned project that you do not need anymore, simply delete or restrict the corresponding API key directly in Google Cloud Console, which cleanly cuts off the endpoint without risking any penalties or disruption to your GitHub account

[nikki-05]

Thank you @Pusri27 , I will try

[justin24er]

Try search across your repos (or all of GitHub if some are public) for the API name, client ID, or key prefix, e.g. org:yourname "AIzaSy" or "googleapis.com/deprecated-api-name". Use github.com/search with "Code" tab, or gh search code via CLI.

once found , check the API's migration guide , Google usually publishes one per deprecation . so update the client library / version. if you don't need it anymore revoke/delete the credential in Cloud console and remove the dependency from the repo. that's it .

and actually, don't forget to test in a branch before merging so nothing breaks live. just in case

[nikki-05]

Thank you @justin24er :)

[al1prahman]

I totally get you and i've been hit with those "API deprecation" emails out of nowhere too. i think tracking down an old project can be super annoying, but some ways I usually handle it:

1. Check GCP first
   Don't bother digging through GitHub just yet. Check the deprecation email. Google usually includes the Project ID in there.
   try to head over to your Google Cloud Console, find that project, and go to APIs & Services > Credentials. Look at your API keys. Usually, we set up restrictions on them (like specific HTTP referrers or IP addresses)

2. GitHub Search Hack
   use GitHub's search bar. Try searching your own repos for things like:
   user:YOUR_USERNAME "googleapis.com" or user:YOUR_USERNAME "client_email" (if you used a service account).
   You can also search specifically in your dependency files (like package.json or requirements.txt) for old Google client libraries.

[nikki-05]

Hey @Pusri27 @justin24er @al1prahman , I have updated my project, but every time I try to navigate to credentials in my dashboard settings, it automatically redirects to the appeal page again. I'm fed up trying. What should I do?

[justin24er]

Ah yeah that's a different beast, that redirect usually means your GCP project itself got flagged/restricted, not just a credentials issue, so it's blocking the whole Credentials page until the appeal is resolved. Sadly there's no dashboard workaround for that, you pretty much have to go through the appeal form itself and wait it out, Google's review queue can take a few days to a couple weeks depending on the flag reason. Worth double checking the appeal email for any specific reason listed (billing, ToS, suspicious activity) so you can address that directly instead of just resubmitting blind. Hang in there!.