-
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
What is the overall story on Connections? #658
Comments
They aren't being phased out and they aren't going anywhere. We've discussed in our meetings that they be stateless and are simply a way to make HTTP requests to the service. Datastore: We allow This was spurred on by comments that there were "too many classes". We realized that we didn't need the typical user to worry about a We still made sure one could be used. Storage: We are in the process of making the API surface easier to use. In this attempt we are trying to "hide" the I've created #632 for my proposal on storage, and @tseaver also made some previous remarks. |
@jgeewax Do we still need this issue open? |
I think you answered the -- closing :) |
* docs: Minor formatting PiperOrigin-RevId: 552790519 Source-Link: googleapis/googleapis@a03330a Source-Link: googleapis/googleapis-gen@4caca49 Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNGNhY2E0OWIzZTA3MzE5MmNiNGEyOTVjMWNmYTFjZjg1MjY2YzI4ZCJ9 * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md * docs: Minor formatting PiperOrigin-RevId: 552837489 Source-Link: googleapis/googleapis@7154a94 Source-Link: googleapis/googleapis-gen@4538a83 Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNDUzOGE4M2EwYTA4N2MzYjFjYzA5MjQ1ZjBlZDg2ODc1ZWI4ODMyZCJ9 * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md --------- Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com> Co-authored-by: Anthonios Partheniou <partheniou@google.com>
I'm noticing that "Connection" objects are slowly being phased out, in favor of
gcloud.<service>.do_thing
(iegcloud.storage.get_bucket()
orgcloud.datastore.Query(...)
).Did we make a specific call to remove the concept of a connection? Was the a discussion somewhere that I can read up on to understand the background behind that?
/cc @tseaver @dhermes
The text was updated successfully, but these errors were encountered: