Package cloud is the root of the packages used to access Google CloudServices. Seehttps://godoc.org/cloud.google.com/go for a full listof sub-packages.

Client Options

All clients in sub-packages are configurable via client options. These options aredescribed here:https://godoc.org/google.golang.org/api/option.

Authentication and Authorization

All the clients in sub-packages support authentication via Google Application DefaultCredentials (seehttps://cloud.google.com/docs/authentication/production), orby providing a JSON key file for a Service Account. See the authentication examplesin this package for details.

Timeouts and Cancellation

By default, non-streaming methods, like Create or Get, will have a default deadline applied to thecontext provided at call time, unless a context deadline is already set. Streamingmethods have no default deadline and will run indefinitely. To set timeouts orarrange for cancellation, use contexts. See the examples for details. Transienterrors will be retried when correctness allows.

To opt out of default deadlines, set the temporary environment variableGOOGLE_API_GO_EXPERIMENTAL_DISABLE_DEFAULT_DEADLINE to "true" prior to clientcreation. This affects all Google Cloud Go client libraries. This opt-outmechanism will be removed in a future release. File an issue athttps://github.com/googleapis/google-cloud-go if the default deadlinescannot work for you.

Do not attempt to control the initial connection (dialing) of a service by setting atimeout on the context passed to NewClient. Dialing is non-blocking, so timeoutswould be ineffective and would only interfere with credential refreshing, which usesthe same context.

Connection Pooling

Connection pooling differs in clients based on their transport. Cloudclients either rely on HTTP or gRPC transports to communicatewith Google Cloud.

Cloud clients that use HTTP (bigquery, compute, storage, and translate) rely on theunderlying HTTP transport to cache connections for later re-use. These are cached tothe default http.MaxIdleConns and http.MaxIdleConnsPerHost settings inhttp.DefaultTransport.

For gRPC clients (all others in this repo), connection pooling is configurable. Usersof cloud client libraries may specify option.WithGRPCConnectionPool(n) as a clientoption to NewClient calls. This configures the underlying gRPC connections to bepooled and addressed in a round robin fashion.

Using the Libraries with Docker

Minimal docker images like Alpine lack CA certificates. This causes RPCs to appear tohang, because gRPC retries indefinitely. Seehttps://github.com/googleapis/google-cloud-go/issues/928for more information.

Debugging

To see gRPC logs, set the environment variable GRPC_GO_LOG_SEVERITY_LEVEL. Seehttps://godoc.org/google.golang.org/grpc/grpclog for more information.

For HTTP logging, set the GODEBUG environment variable to "http2debug=1" or "http2debug=2".

Inspecting errors

Most of the errors returned by the generated clients can be converted into agrpc.Status. Converting your errors to this type can be a useful to getmore information about what went wrong while debugging.

iferr!={ifs,ok:=status.FromError(err);ok{log.Println(s.Message())for_,d:=ranges.Proto().Details{log.Println(d)}}}

Client Stability

Clients in this repository are considered alpha or beta unless otherwisemarked as stable in the README.md. Semver is not used to communicate stabilityof clients.

Alpha and beta clients may change or go away without notice.

Clients marked stable will maintain compatibility with future versions for aslong as we can reasonably sustain. Incompatible changes might be made in somesituations, including:

- Security bugs may prompt backwards-incompatible changes.

- Situations in which components are no longer feasible to maintain withoutmaking breaking changes, including removal.

- Parts of the client surface may be outright unstable and subject to change.These parts of the surface will be labeled with the note, "It is EXPERIMENTALand subject to change or removal without notice."