terraform/vendor/google.golang.org/grpc
Paddy 5127f1ef8b
command: Unmanaged providers
This adds supports for "unmanaged" providers, or providers with process
lifecycles not controlled by Terraform. These providers are assumed to
be started before Terraform is launched, and are assumed to shut
themselves down after Terraform has finished running.

To do this, we must update the go-plugin dependency to v1.3.0, which
added support for the "test mode" plugin serving that powers all this.

As a side-effect of not needing to manage the process lifecycle anymore,
Terraform also no longer needs to worry about the provider's binary, as
it won't be used for anything anymore. Because of this, we can disable
the init behavior that concerns itself with downloading that provider's
binary, checking its version, and otherwise managing the binary.

This is all managed on a per-provider basis, so managed providers that
Terraform downloads, starts, and stops can be used in the same commands
as unmanaged providers. The TF_REATTACH_PROVIDERS environment variable
is added, and is a JSON encoding of the provider's address to the
information we need to connect to it.

This change enables two benefits: first, delve and other debuggers can
now be attached to provider server processes, and Terraform can connect.
This allows for attaching debuggers to provider processes, which before
was difficult to impossible. Second, it allows the SDK test framework to
host the provider in the same process as the test driver, while running
a production Terraform binary against the provider. This allows for Go's
built-in race detector and test coverage tooling to work as expected in
provider tests.

Unmanaged providers are expected to work in the exact same way as
managed providers, with one caveat: Terraform kills provider processes
and restarts them once per graph walk, meaning multiple times during
most Terraform CLI commands. As unmanaged providers can't be killed by
Terraform, and have no visibility into graph walks, unmanaged providers
are likely to have differences in how their global mutable state behaves
when compared to managed providers. Namely, unmanaged providers are
likely to retain global state when managed providers would have reset
it. Developers relying on global state should be aware of this.
2020-05-26 17:48:57 -07:00
..
attributes command: Unmanaged providers 2020-05-26 17:48:57 -07:00
backoff command: Unmanaged providers 2020-05-26 17:48:57 -07:00
balancer command: Unmanaged providers 2020-05-26 17:48:57 -07:00
binarylog/grpc_binarylog_v1
codes
connectivity
credentials command: Unmanaged providers 2020-05-26 17:48:57 -07:00
encoding command: Unmanaged providers 2020-05-26 17:48:57 -07:00
grpclog command: Unmanaged providers 2020-05-26 17:48:57 -07:00
health command: Unmanaged providers 2020-05-26 17:48:57 -07:00
internal command: Unmanaged providers 2020-05-26 17:48:57 -07:00
keepalive
metadata
naming command: Unmanaged providers 2020-05-26 17:48:57 -07:00
peer
reflection command: Unmanaged providers 2020-05-26 17:48:57 -07:00
resolver command: Unmanaged providers 2020-05-26 17:48:57 -07:00
serviceconfig command: Unmanaged providers 2020-05-26 17:48:57 -07:00
stats command: Unmanaged providers 2020-05-26 17:48:57 -07:00
status command: Unmanaged providers 2020-05-26 17:48:57 -07:00
tap
test/bufconn command: Unmanaged providers 2020-05-26 17:48:57 -07:00
.travis.yml command: Unmanaged providers 2020-05-26 17:48:57 -07:00
AUTHORS
CODE-OF-CONDUCT.md command: Unmanaged providers 2020-05-26 17:48:57 -07:00
CONTRIBUTING.md command: Unmanaged providers 2020-05-26 17:48:57 -07:00
GOVERNANCE.md command: Unmanaged providers 2020-05-26 17:48:57 -07:00
LICENSE
MAINTAINERS.md command: Unmanaged providers 2020-05-26 17:48:57 -07:00
Makefile command: Unmanaged providers 2020-05-26 17:48:57 -07:00
README.md
backoff.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
balancer.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
balancer_conn_wrappers.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
balancer_v1_wrapper.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
call.go
clientconn.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
codec.go
codegen.sh
dialoptions.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
doc.go
go.mod command: Unmanaged providers 2020-05-26 17:48:57 -07:00
go.sum command: Unmanaged providers 2020-05-26 17:48:57 -07:00
install_gae.sh
interceptor.go
picker_wrapper.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
pickfirst.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
preloader.go
proxy.go
resolver_conn_wrapper.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
rpc_util.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
server.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
service_config.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
stream.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
trace.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
version.go command: Unmanaged providers 2020-05-26 17:48:57 -07:00
vet.sh command: Unmanaged providers 2020-05-26 17:48:57 -07:00

README.md

gRPC-Go

Build Status GoDoc GoReportCard

The Go implementation of gRPC: A high performance, open source, general RPC framework that puts mobile and HTTP/2 first. For more information see the gRPC Quick Start: Go guide.

Installation

To install this package, you need to install Go and setup your Go workspace on your computer. The simplest way to install the library is to run:

$ go get -u google.golang.org/grpc

With Go module support (Go 1.11+), simply import "google.golang.org/grpc" in your source code and go [build|run|test] will automatically download the necessary dependencies (Go modules ref).

If you are trying to access grpc-go from within China, please see the FAQ below.

Prerequisites

gRPC-Go requires Go 1.9 or later.

Documentation

Performance

Performance benchmark data for grpc-go and other languages is maintained in this dashboard.

Status

General Availability Google Cloud Platform Launch Stages.

FAQ

I/O Timeout Errors

The golang.org domain may be blocked from some countries. go get usually produces an error like the following when this happens:

$ go get -u google.golang.org/grpc
package google.golang.org/grpc: unrecognized import path "google.golang.org/grpc" (https fetch: Get https://google.golang.org/grpc?go-get=1: dial tcp 216.239.37.1:443: i/o timeout)

To build Go code, there are several options:

  • Set up a VPN and access google.golang.org through that.

  • Without Go module support: git clone the repo manually:

    git clone https://github.com/grpc/grpc-go.git $GOPATH/src/google.golang.org/grpc
    

    You will need to do the same for all of grpc's dependencies in golang.org, e.g. golang.org/x/net.

  • With Go module support: it is possible to use the replace feature of go mod to create aliases for golang.org packages. In your project's directory:

    go mod edit -replace=google.golang.org/grpc=github.com/grpc/grpc-go@latest
    go mod tidy
    go mod vendor
    go build -mod=vendor
    

    Again, this will need to be done for all transitive dependencies hosted on golang.org as well. Please refer to this issue in the golang repo regarding this concern.

Compiling error, undefined: grpc.SupportPackageIsVersion

Please update proto package, gRPC package and rebuild the proto files:

  • go get -u github.com/golang/protobuf/{proto,protoc-gen-go}
  • go get -u google.golang.org/grpc
  • protoc --go_out=plugins=grpc:. *.proto

How to turn on logging

The default logger is controlled by the environment variables. Turn everything on by setting:

GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info

The RPC failed with error "code = Unavailable desc = transport is closing"

This error means the connection the RPC is using was closed, and there are many possible reasons, including:

  1. mis-configured transport credentials, connection failed on handshaking
  2. bytes disrupted, possibly by a proxy in between
  3. server shutdown

It can be tricky to debug this because the error happens on the client side but the root cause of the connection being closed is on the server side. Turn on logging on both client and server, and see if there are any transport errors.