A tiny read-only CLI for checking whether Google Cloud Application Default Credentials are usable from your local environment.
It is meant for the boring but common situation where a local script, notebook, or internal tool fails and you need to quickly answer:
- Are Application Default Credentials available?
- Can the credentials be refreshed?
- Can this identity read BigQuery metadata for a project?
- Can this identity access a specific Cloud Storage bucket?
The tool does not create, update, or delete Google Cloud resources.
From a local checkout:
pip install -e .For development:
pip install -e '.[dev]'This tool uses Google Application Default Credentials.
gcloud auth application-default loginIf your environment does not provide a default project, pass one explicitly with --project.
Check that ADC loads and refreshes:
gcp-adc-smoke-testCheck BigQuery access for a project:
gcp-adc-smoke-test --project my-gcp-project --bigqueryCheck a Cloud Storage bucket:
gcp-adc-smoke-test \
--project my-gcp-project \
--storage-bucket my-bucketCheck both BigQuery and Storage:
gcp-adc-smoke-test \
--project my-gcp-project \
--bigquery \
--storage-bucket my-bucketExample output:
GCP ADC Smoke Test
[OK] Application Default Credentials: ADC loaded successfully.
[OK] Credential identity: Resolved credential identity: user@example.com
[OK] BigQuery access: BigQuery access confirmed for project: my-gcp-project
[OK] Cloud Storage bucket access: Storage bucket access confirmed: my-bucket
All requested checks passed.
Some credential types do not expose a stable email or service account identity. In that case, the identity check may report that credentials are valid but the identity is not exposed.
- Read-only checks only
- No service account key management
- No credential storage
- No OAuth setup wizard
- No broad resource inventory
- Intended for local diagnostics before running scripts or internal tools
Run tests:
pytestRun linting:
ruff check .Run type checking:
mypy srcMIT