-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding optional switch to capture project ID in from_service_account_json(). #3436
Conversation
It would be great to solve this by just consolidating |
@jonparrott See the table I made about usage. The only issue with that is some APIs don't use a project (and we don't want to fail their constructors over a missing project). |
Does it help that google auth doesn't error if it can't determine a project?
|
@jonparrott Mostly it doesn't help because it isn't true? Or do you mean something else? |
That's if it doesn't find credentials, not if it doesn't find the project.
|
But there is no |
Right. This is part of the constraint. You should never get a project ID that didn't come from the same source as the credentials.
|
Makes sense. @lukesneeringer WDYT of us just using |
FTR, $ for f in $(ls */google/cloud/*/client.py); do
if ! grep -q ClientWithProject $f; then
echo $f
fi
done
bigtable/google/cloud/bigtable/client.py
language/google/cloud/language/client.py
resource_manager/google/cloud/resource_manager/client.py
spanner/google/cloud/spanner/client.py
speech/google/cloud/speech/client.py
translate/google/cloud/translate/client.py Of those, the following have $ for f in $(ls */google/cloud/*/client.py); do
if ! grep -q ClientWithProject $f; then
echo $f
fi
done | xargs grep -l _ClientProjectMixin
bigtable/google/cloud/bigtable/client.py
spanner/google/cloud/spanner/client.py |
# Check that mocks were called as expected. | ||
file_open.assert_called_once_with( | ||
mock.sentinel.filename, 'r', encoding='utf-8') | ||
constructor.assert_called_once_with(info) |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
@tseaver Sorry I missed your LGTM 18 days ago. It's good I got this in, in case we have a |
…rm/python-docs-samples#3436) * [container_registry] fix: fix broken test fixes #3435 * Use Pub/Sub message receiver that can notify main thread when it has received expected number of messages. * Only test one single occurence. * Use uuid4 wherever makes sense. * test if Pub/Sub client receives at least one message
Fixes #1883.
@lukesneeringer This is a long-standing bug but should really make it into a
google-cloud-core
release. I know you hate releasingcore
.