2018-09-24 18:30:39 +02:00
|
|
|
#!/bin/bash
|
|
|
|
|
|
|
|
if [[ `uname -a` = *"Darwin"* ]]; then
|
|
|
|
echo "It seems you are running on Mac. This script does not work on Mac. See https://github.com/grpc/grpc-go/issues/2047"
|
|
|
|
exit 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
set -ex # Exit on error; debugging enabled.
|
|
|
|
set -o pipefail # Fail a pipe if any sub-command fails.
|
|
|
|
|
|
|
|
die() {
|
|
|
|
echo "$@" >&2
|
|
|
|
exit 1
|
|
|
|
}
|
|
|
|
|
2019-07-30 00:19:40 +02:00
|
|
|
fail_on_output() {
|
|
|
|
tee /dev/stderr | (! read)
|
|
|
|
}
|
2019-02-20 19:51:33 +01:00
|
|
|
|
2019-07-30 00:19:40 +02:00
|
|
|
# Check to make sure it's safe to modify the user's git repo.
|
|
|
|
git status --porcelain | fail_on_output
|
2019-02-20 19:51:33 +01:00
|
|
|
|
|
|
|
# Undo any edits made by this script.
|
|
|
|
cleanup() {
|
|
|
|
git reset --hard HEAD
|
|
|
|
}
|
|
|
|
trap cleanup EXIT
|
|
|
|
|
|
|
|
PATH="${GOPATH}/bin:${GOROOT}/bin:${PATH}"
|
|
|
|
|
|
|
|
if [[ "$1" = "-install" ]]; then
|
|
|
|
# Check for module support
|
|
|
|
if go help mod >& /dev/null; then
|
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-27 02:48:57 +02:00
|
|
|
# Install the pinned versions as defined in module tools.
|
|
|
|
pushd ./test/tools
|
2019-02-20 19:51:33 +01:00
|
|
|
go install \
|
|
|
|
golang.org/x/lint/golint \
|
|
|
|
golang.org/x/tools/cmd/goimports \
|
|
|
|
honnef.co/go/tools/cmd/staticcheck \
|
|
|
|
github.com/client9/misspell/cmd/misspell \
|
|
|
|
github.com/golang/protobuf/protoc-gen-go
|
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-27 02:48:57 +02:00
|
|
|
popd
|
2019-02-20 19:51:33 +01:00
|
|
|
else
|
|
|
|
# Ye olde `go get` incantation.
|
|
|
|
# Note: this gets the latest version of all tools (vs. the pinned versions
|
|
|
|
# with Go modules).
|
|
|
|
go get -u \
|
|
|
|
golang.org/x/lint/golint \
|
|
|
|
golang.org/x/tools/cmd/goimports \
|
|
|
|
honnef.co/go/tools/cmd/staticcheck \
|
|
|
|
github.com/client9/misspell/cmd/misspell \
|
|
|
|
github.com/golang/protobuf/protoc-gen-go
|
|
|
|
fi
|
|
|
|
if [[ -z "${VET_SKIP_PROTO}" ]]; then
|
|
|
|
if [[ "${TRAVIS}" = "true" ]]; then
|
2018-09-24 18:30:39 +02:00
|
|
|
PROTOBUF_VERSION=3.3.0
|
|
|
|
PROTOC_FILENAME=protoc-${PROTOBUF_VERSION}-linux-x86_64.zip
|
|
|
|
pushd /home/travis
|
|
|
|
wget https://github.com/google/protobuf/releases/download/v${PROTOBUF_VERSION}/${PROTOC_FILENAME}
|
|
|
|
unzip ${PROTOC_FILENAME}
|
|
|
|
bin/protoc --version
|
|
|
|
popd
|
|
|
|
elif ! which protoc > /dev/null; then
|
|
|
|
die "Please install protoc into your path"
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
exit 0
|
|
|
|
elif [[ "$#" -ne 0 ]]; then
|
|
|
|
die "Unknown argument(s): $*"
|
|
|
|
fi
|
|
|
|
|
2019-02-20 19:51:33 +01:00
|
|
|
# - Ensure all source files contain a copyright message.
|
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-27 02:48:57 +02:00
|
|
|
(! git grep -L "\(Copyright [0-9]\{4,\} gRPC authors\)\|DO NOT EDIT" -- '*.go')
|
2018-09-24 18:30:39 +02:00
|
|
|
|
2019-02-20 19:51:33 +01:00
|
|
|
# - Make sure all tests in grpc and grpc/test use leakcheck via Teardown.
|
|
|
|
(! grep 'func Test[^(]' *_test.go)
|
|
|
|
(! grep 'func Test[^(]' test/*.go)
|
2018-09-24 18:30:39 +02:00
|
|
|
|
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-27 02:48:57 +02:00
|
|
|
# - Do not import x/net/context.
|
|
|
|
(! git grep -l 'x/net/context' -- "*.go")
|
|
|
|
|
2019-02-20 19:51:33 +01:00
|
|
|
# - Do not import math/rand for real library code. Use internal/grpcrand for
|
|
|
|
# thread safety.
|
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-27 02:48:57 +02:00
|
|
|
git grep -l '"math/rand"' -- "*.go" 2>&1 | (! grep -v '^examples\|^stress\|grpcrand\|^benchmark\|wrr_test')
|
2018-09-24 18:30:39 +02:00
|
|
|
|
2019-02-20 19:51:33 +01:00
|
|
|
# - Ensure all ptypes proto packages are renamed when importing.
|
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-27 02:48:57 +02:00
|
|
|
(! git grep "\(import \|^\s*\)\"github.com/golang/protobuf/ptypes/" -- "*.go")
|
2019-02-20 19:51:33 +01:00
|
|
|
|
|
|
|
# - Check imports that are illegal in appengine (until Go 1.11).
|
|
|
|
# TODO: Remove when we drop Go 1.10 support
|
|
|
|
go list -f {{.Dir}} ./... | xargs go run test/go_vet/vet.go
|
|
|
|
|
|
|
|
# - gofmt, goimports, golint (with exceptions for generated code), go vet.
|
|
|
|
gofmt -s -d -l . 2>&1 | fail_on_output
|
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-27 02:48:57 +02:00
|
|
|
goimports -l . 2>&1 | (! grep -vE "(_mock|\.pb)\.go")
|
2019-02-20 19:51:33 +01:00
|
|
|
golint ./... 2>&1 | (! grep -vE "(_mock|\.pb)\.go:")
|
2019-09-09 14:04:58 +02:00
|
|
|
go vet -all .
|
2019-02-20 19:51:33 +01:00
|
|
|
|
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-27 02:48:57 +02:00
|
|
|
misspell -error .
|
|
|
|
|
2019-02-20 19:51:33 +01:00
|
|
|
# - Check that generated proto files are up to date.
|
|
|
|
if [[ -z "${VET_SKIP_PROTO}" ]]; then
|
|
|
|
PATH="/home/travis/bin:${PATH}" make proto && \
|
|
|
|
git status --porcelain 2>&1 | fail_on_output || \
|
2018-09-24 18:30:39 +02:00
|
|
|
(git status; git --no-pager diff; exit 1)
|
|
|
|
fi
|
|
|
|
|
2019-02-20 19:51:33 +01:00
|
|
|
# - Check that our module is tidy.
|
|
|
|
if go help mod >& /dev/null; then
|
|
|
|
go mod tidy && \
|
|
|
|
git status --porcelain 2>&1 | fail_on_output || \
|
|
|
|
(git status; git --no-pager diff; exit 1)
|
|
|
|
fi
|
|
|
|
|
|
|
|
# - Collection of static analysis checks
|
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-27 02:48:57 +02:00
|
|
|
#
|
|
|
|
# TODO(dfawley): don't use deprecated functions in examples or first-party
|
|
|
|
# plugins.
|
|
|
|
SC_OUT="$(mktemp)"
|
|
|
|
staticcheck -go 1.9 -checks 'inherit,-ST1015' ./... > "${SC_OUT}" || true
|
|
|
|
# Error if anything other than deprecation warnings are printed.
|
|
|
|
(! grep -v "is deprecated:.*SA1019" "${SC_OUT}")
|
|
|
|
# Only ignore the following deprecated types/fields/functions.
|
|
|
|
(! grep -Fv '.HandleResolvedAddrs
|
|
|
|
.HandleSubConnStateChange
|
|
|
|
.HeaderMap
|
|
|
|
.NewAddress
|
|
|
|
.NewServiceConfig
|
|
|
|
.Metadata is deprecated: use Attributes
|
|
|
|
.Type is deprecated: use Attributes
|
|
|
|
.UpdateBalancerState
|
|
|
|
balancer.Picker
|
|
|
|
grpc.CallCustomCodec
|
|
|
|
grpc.Code
|
|
|
|
grpc.Compressor
|
|
|
|
grpc.Decompressor
|
|
|
|
grpc.MaxMsgSize
|
|
|
|
grpc.MethodConfig
|
|
|
|
grpc.NewGZIPCompressor
|
|
|
|
grpc.NewGZIPDecompressor
|
|
|
|
grpc.RPCCompressor
|
|
|
|
grpc.RPCDecompressor
|
|
|
|
grpc.RoundRobin
|
|
|
|
grpc.ServiceConfig
|
|
|
|
grpc.WithBalancer
|
|
|
|
grpc.WithBalancerName
|
|
|
|
grpc.WithCompressor
|
|
|
|
grpc.WithDecompressor
|
|
|
|
grpc.WithDialer
|
|
|
|
grpc.WithMaxMsgSize
|
|
|
|
grpc.WithServiceConfig
|
|
|
|
grpc.WithTimeout
|
|
|
|
http.CloseNotifier
|
|
|
|
naming.Resolver
|
|
|
|
naming.Update
|
|
|
|
naming.Watcher
|
|
|
|
resolver.Backend
|
|
|
|
resolver.GRPCLB' "${SC_OUT}"
|
|
|
|
)
|