-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Adding auto create to pub/sub topic. #949
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
Conversation
|
To be honest, in python looking before you leap isn't as overly onerous as it is in node: So I'm okay with nixing this if the cost/benefit isn't good. My only issue now is that the check for exists is slow, but that's not this library's fault. |
|
@jonparrott Sorry for the huge delay in reply. Since it was @waprin who filed, I want to feel out for how he feels about closing #905. Also I noticed on googleapis/google-cloud-node#696 that you and @tmatsuo are having some reservations of |
|
Yeah in retrospect auto_create creates more confusion than convenience, I'm fine with just closing them all down. |
|
Thanks guys! Let me know if there is anything we can do to make the sample writing process easier. |
…tion (#949) * add partitioning and clustering to the to_gbq function * feat: add partitioning and clustering to the to_gbq function * added tests * fixed documentation error * run nox -r -s format lint --------- Co-authored-by: Tim Sweña (Swast) <swast@google.com>
* chore(python): Add Python 3.12 * feat: Add Python 3.12 * Allow extra log message in cache tests.
🤖 I have created a release *beep* *boop* --- ## [2.4.0](googleapis/google-auth-library-python@v2.3.3...v2.4.0) (2022-01-20) ### Features * add 'py.typed' declaration ([#919](googleapis/google-auth-library-python#919)) ([c993504](googleapis/google-auth-library-python@c993504)) * add api key support ([#826](googleapis/google-auth-library-python#826)) ([3b15092](googleapis/google-auth-library-python@3b15092)) ### Bug Fixes * **deps:** allow cachetools 5.0 for python 3.7+ ([#937](googleapis/google-auth-library-python#937)) ([1eae37d](googleapis/google-auth-library-python@1eae37d)) * fix the message format for metadata server exception ([#916](googleapis/google-auth-library-python#916)) ([e756f08](googleapis/google-auth-library-python@e756f08)) ### Documentation * fix intersphinx link for 'requests-oauthlib' ([#921](googleapis/google-auth-library-python#921)) ([967be4f](googleapis/google-auth-library-python@967be4f)) * note ValueError in `verify_oauth2_token` ([#928](googleapis/google-auth-library-python#928)) ([82bc5f0](googleapis/google-auth-library-python@82bc5f0)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Fixes #905.
This is labelled
don't mergebecause it doesn't adhere to the truly optimal case described in #905 by @jonparrott. I sent the PR just to have more discussion here (now that @tseaver is back in the US).I'm worried that implementing the method used by node will be painful. I suppose we could do it with something like a custom class that is just bound to the
topicand calls made for itBUT, no matter how I slice it, the added complexity doesn't seem to be worth it for a measly feature like
auto_create. But maybe I am undervaluing it?