2018-09-24 18:30:39 +02:00
|
|
|
/*
|
|
|
|
*
|
|
|
|
* Copyright 2017 gRPC authors.
|
|
|
|
*
|
|
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
* you may not use this file except in compliance with the License.
|
|
|
|
* You may obtain a copy of the License at
|
|
|
|
*
|
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
*
|
|
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
* See the License for the specific language governing permissions and
|
|
|
|
* limitations under the License.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
package grpc
|
|
|
|
|
|
|
|
import (
|
|
|
|
"sync"
|
|
|
|
|
|
|
|
"google.golang.org/grpc/balancer"
|
|
|
|
"google.golang.org/grpc/connectivity"
|
|
|
|
"google.golang.org/grpc/grpclog"
|
|
|
|
"google.golang.org/grpc/resolver"
|
|
|
|
)
|
|
|
|
|
|
|
|
type balancerWrapperBuilder struct {
|
|
|
|
b Balancer // The v1 balancer.
|
|
|
|
}
|
|
|
|
|
|
|
|
func (bwb *balancerWrapperBuilder) Build(cc balancer.ClientConn, opts balancer.BuildOptions) balancer.Balancer {
|
2019-09-09 14:04:58 +02:00
|
|
|
bwb.b.Start(opts.Target.Endpoint, BalancerConfig{
|
2018-09-24 18:30:39 +02:00
|
|
|
DialCreds: opts.DialCreds,
|
|
|
|
Dialer: opts.Dialer,
|
|
|
|
})
|
|
|
|
_, pickfirst := bwb.b.(*pickFirst)
|
|
|
|
bw := &balancerWrapper{
|
|
|
|
balancer: bwb.b,
|
|
|
|
pickfirst: pickfirst,
|
|
|
|
cc: cc,
|
2019-09-09 14:04:58 +02:00
|
|
|
targetAddr: opts.Target.Endpoint,
|
2018-09-24 18:30:39 +02:00
|
|
|
startCh: make(chan struct{}),
|
|
|
|
conns: make(map[resolver.Address]balancer.SubConn),
|
|
|
|
connSt: make(map[balancer.SubConn]*scState),
|
|
|
|
csEvltr: &balancer.ConnectivityStateEvaluator{},
|
|
|
|
state: connectivity.Idle,
|
|
|
|
}
|
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
|
|
|
cc.UpdateState(balancer.State{ConnectivityState: connectivity.Idle, Picker: bw})
|
2018-09-24 18:30:39 +02:00
|
|
|
go bw.lbWatcher()
|
|
|
|
return bw
|
|
|
|
}
|
|
|
|
|
|
|
|
func (bwb *balancerWrapperBuilder) Name() string {
|
|
|
|
return "wrapper"
|
|
|
|
}
|
|
|
|
|
|
|
|
type scState struct {
|
|
|
|
addr Address // The v1 address type.
|
|
|
|
s connectivity.State
|
|
|
|
down func(error)
|
|
|
|
}
|
|
|
|
|
|
|
|
type balancerWrapper struct {
|
|
|
|
balancer Balancer // The v1 balancer.
|
|
|
|
pickfirst bool
|
|
|
|
|
|
|
|
cc balancer.ClientConn
|
|
|
|
targetAddr string // Target without the scheme.
|
|
|
|
|
|
|
|
mu sync.Mutex
|
|
|
|
conns map[resolver.Address]balancer.SubConn
|
|
|
|
connSt map[balancer.SubConn]*scState
|
|
|
|
// This channel is closed when handling the first resolver result.
|
|
|
|
// lbWatcher blocks until this is closed, to avoid race between
|
|
|
|
// - NewSubConn is created, cc wants to notify balancer of state changes;
|
|
|
|
// - Build hasn't return, cc doesn't have access to balancer.
|
|
|
|
startCh chan struct{}
|
|
|
|
|
|
|
|
// To aggregate the connectivity state.
|
|
|
|
csEvltr *balancer.ConnectivityStateEvaluator
|
|
|
|
state connectivity.State
|
|
|
|
}
|
|
|
|
|
|
|
|
// lbWatcher watches the Notify channel of the balancer and manages
|
|
|
|
// connections accordingly.
|
|
|
|
func (bw *balancerWrapper) lbWatcher() {
|
|
|
|
<-bw.startCh
|
|
|
|
notifyCh := bw.balancer.Notify()
|
|
|
|
if notifyCh == nil {
|
|
|
|
// There's no resolver in the balancer. Connect directly.
|
|
|
|
a := resolver.Address{
|
|
|
|
Addr: bw.targetAddr,
|
|
|
|
Type: resolver.Backend,
|
|
|
|
}
|
|
|
|
sc, err := bw.cc.NewSubConn([]resolver.Address{a}, balancer.NewSubConnOptions{})
|
|
|
|
if err != nil {
|
|
|
|
grpclog.Warningf("Error creating connection to %v. Err: %v", a, err)
|
|
|
|
} else {
|
|
|
|
bw.mu.Lock()
|
|
|
|
bw.conns[a] = sc
|
|
|
|
bw.connSt[sc] = &scState{
|
|
|
|
addr: Address{Addr: bw.targetAddr},
|
|
|
|
s: connectivity.Idle,
|
|
|
|
}
|
|
|
|
bw.mu.Unlock()
|
|
|
|
sc.Connect()
|
|
|
|
}
|
|
|
|
return
|
|
|
|
}
|
|
|
|
|
|
|
|
for addrs := range notifyCh {
|
2019-09-09 14:04:58 +02:00
|
|
|
grpclog.Infof("balancerWrapper: got update addr from Notify: %v", addrs)
|
2018-09-24 18:30:39 +02:00
|
|
|
if bw.pickfirst {
|
|
|
|
var (
|
|
|
|
oldA resolver.Address
|
|
|
|
oldSC balancer.SubConn
|
|
|
|
)
|
|
|
|
bw.mu.Lock()
|
|
|
|
for oldA, oldSC = range bw.conns {
|
|
|
|
break
|
|
|
|
}
|
|
|
|
bw.mu.Unlock()
|
|
|
|
if len(addrs) <= 0 {
|
|
|
|
if oldSC != nil {
|
|
|
|
// Teardown old sc.
|
|
|
|
bw.mu.Lock()
|
|
|
|
delete(bw.conns, oldA)
|
|
|
|
delete(bw.connSt, oldSC)
|
|
|
|
bw.mu.Unlock()
|
|
|
|
bw.cc.RemoveSubConn(oldSC)
|
|
|
|
}
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
|
|
|
|
var newAddrs []resolver.Address
|
|
|
|
for _, a := range addrs {
|
|
|
|
newAddr := resolver.Address{
|
|
|
|
Addr: a.Addr,
|
|
|
|
Type: resolver.Backend, // All addresses from balancer are all backends.
|
|
|
|
ServerName: "",
|
|
|
|
Metadata: a.Metadata,
|
|
|
|
}
|
|
|
|
newAddrs = append(newAddrs, newAddr)
|
|
|
|
}
|
|
|
|
if oldSC == nil {
|
|
|
|
// Create new sc.
|
|
|
|
sc, err := bw.cc.NewSubConn(newAddrs, balancer.NewSubConnOptions{})
|
|
|
|
if err != nil {
|
|
|
|
grpclog.Warningf("Error creating connection to %v. Err: %v", newAddrs, err)
|
|
|
|
} else {
|
|
|
|
bw.mu.Lock()
|
|
|
|
// For pickfirst, there should be only one SubConn, so the
|
|
|
|
// address doesn't matter. All states updating (up and down)
|
|
|
|
// and picking should all happen on that only SubConn.
|
|
|
|
bw.conns[resolver.Address{}] = sc
|
|
|
|
bw.connSt[sc] = &scState{
|
|
|
|
addr: addrs[0], // Use the first address.
|
|
|
|
s: connectivity.Idle,
|
|
|
|
}
|
|
|
|
bw.mu.Unlock()
|
|
|
|
sc.Connect()
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
bw.mu.Lock()
|
|
|
|
bw.connSt[oldSC].addr = addrs[0]
|
|
|
|
bw.mu.Unlock()
|
|
|
|
oldSC.UpdateAddresses(newAddrs)
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
var (
|
|
|
|
add []resolver.Address // Addresses need to setup connections.
|
|
|
|
del []balancer.SubConn // Connections need to tear down.
|
|
|
|
)
|
|
|
|
resAddrs := make(map[resolver.Address]Address)
|
|
|
|
for _, a := range addrs {
|
|
|
|
resAddrs[resolver.Address{
|
|
|
|
Addr: a.Addr,
|
|
|
|
Type: resolver.Backend, // All addresses from balancer are all backends.
|
|
|
|
ServerName: "",
|
|
|
|
Metadata: a.Metadata,
|
|
|
|
}] = a
|
|
|
|
}
|
|
|
|
bw.mu.Lock()
|
|
|
|
for a := range resAddrs {
|
|
|
|
if _, ok := bw.conns[a]; !ok {
|
|
|
|
add = append(add, a)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
for a, c := range bw.conns {
|
|
|
|
if _, ok := resAddrs[a]; !ok {
|
|
|
|
del = append(del, c)
|
|
|
|
delete(bw.conns, a)
|
|
|
|
// Keep the state of this sc in bw.connSt until its state becomes Shutdown.
|
|
|
|
}
|
|
|
|
}
|
|
|
|
bw.mu.Unlock()
|
|
|
|
for _, a := range add {
|
|
|
|
sc, err := bw.cc.NewSubConn([]resolver.Address{a}, balancer.NewSubConnOptions{})
|
|
|
|
if err != nil {
|
|
|
|
grpclog.Warningf("Error creating connection to %v. Err: %v", a, err)
|
|
|
|
} else {
|
|
|
|
bw.mu.Lock()
|
|
|
|
bw.conns[a] = sc
|
|
|
|
bw.connSt[sc] = &scState{
|
|
|
|
addr: resAddrs[a],
|
|
|
|
s: connectivity.Idle,
|
|
|
|
}
|
|
|
|
bw.mu.Unlock()
|
|
|
|
sc.Connect()
|
|
|
|
}
|
|
|
|
}
|
|
|
|
for _, c := range del {
|
|
|
|
bw.cc.RemoveSubConn(c)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
func (bw *balancerWrapper) HandleSubConnStateChange(sc balancer.SubConn, s connectivity.State) {
|
|
|
|
bw.mu.Lock()
|
|
|
|
defer bw.mu.Unlock()
|
|
|
|
scSt, ok := bw.connSt[sc]
|
|
|
|
if !ok {
|
|
|
|
return
|
|
|
|
}
|
|
|
|
if s == connectivity.Idle {
|
|
|
|
sc.Connect()
|
|
|
|
}
|
|
|
|
oldS := scSt.s
|
|
|
|
scSt.s = s
|
|
|
|
if oldS != connectivity.Ready && s == connectivity.Ready {
|
|
|
|
scSt.down = bw.balancer.Up(scSt.addr)
|
|
|
|
} else if oldS == connectivity.Ready && s != connectivity.Ready {
|
|
|
|
if scSt.down != nil {
|
|
|
|
scSt.down(errConnClosing)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
sa := bw.csEvltr.RecordTransition(oldS, s)
|
|
|
|
if bw.state != sa {
|
|
|
|
bw.state = sa
|
|
|
|
}
|
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
|
|
|
bw.cc.UpdateState(balancer.State{ConnectivityState: bw.state, Picker: bw})
|
2018-09-24 18:30:39 +02:00
|
|
|
if s == connectivity.Shutdown {
|
|
|
|
// Remove state for this sc.
|
|
|
|
delete(bw.connSt, sc)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
func (bw *balancerWrapper) HandleResolvedAddrs([]resolver.Address, error) {
|
|
|
|
bw.mu.Lock()
|
|
|
|
defer bw.mu.Unlock()
|
|
|
|
select {
|
|
|
|
case <-bw.startCh:
|
|
|
|
default:
|
|
|
|
close(bw.startCh)
|
|
|
|
}
|
|
|
|
// There should be a resolver inside the balancer.
|
|
|
|
// All updates here, if any, are ignored.
|
|
|
|
}
|
|
|
|
|
|
|
|
func (bw *balancerWrapper) Close() {
|
|
|
|
bw.mu.Lock()
|
|
|
|
defer bw.mu.Unlock()
|
|
|
|
select {
|
|
|
|
case <-bw.startCh:
|
|
|
|
default:
|
|
|
|
close(bw.startCh)
|
|
|
|
}
|
|
|
|
bw.balancer.Close()
|
|
|
|
}
|
|
|
|
|
|
|
|
// The picker is the balancerWrapper itself.
|
|
|
|
// It either blocks or returns error, consistent with v1 balancer Get().
|
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
|
|
|
func (bw *balancerWrapper) Pick(info balancer.PickInfo) (result balancer.PickResult, err error) {
|
2018-09-24 18:30:39 +02:00
|
|
|
failfast := true // Default failfast is true.
|
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
|
|
|
if ss, ok := rpcInfoFromContext(info.Ctx); ok {
|
2018-09-24 18:30:39 +02:00
|
|
|
failfast = ss.failfast
|
|
|
|
}
|
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
|
|
|
a, p, err := bw.balancer.Get(info.Ctx, BalancerGetOptions{BlockingWait: !failfast})
|
2018-09-24 18:30:39 +02:00
|
|
|
if err != nil {
|
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
|
|
|
return balancer.PickResult{}, toRPCErr(err)
|
2018-09-24 18:30:39 +02:00
|
|
|
}
|
|
|
|
if p != nil {
|
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
|
|
|
result.Done = func(balancer.DoneInfo) { p() }
|
2019-07-30 00:19:40 +02:00
|
|
|
defer func() {
|
|
|
|
if err != nil {
|
|
|
|
p()
|
|
|
|
}
|
|
|
|
}()
|
2018-09-24 18:30:39 +02:00
|
|
|
}
|
2019-07-30 00:19:40 +02:00
|
|
|
|
2018-09-24 18:30:39 +02:00
|
|
|
bw.mu.Lock()
|
|
|
|
defer bw.mu.Unlock()
|
|
|
|
if bw.pickfirst {
|
|
|
|
// Get the first sc in conns.
|
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
|
|
|
for _, result.SubConn = range bw.conns {
|
|
|
|
return result, nil
|
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
|
|
|
return balancer.PickResult{}, balancer.ErrNoSubConnAvailable
|
2019-07-30 00:19:40 +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
|
|
|
var ok1 bool
|
|
|
|
result.SubConn, ok1 = bw.conns[resolver.Address{
|
2019-07-30 00:19:40 +02:00
|
|
|
Addr: a.Addr,
|
|
|
|
Type: resolver.Backend,
|
|
|
|
ServerName: "",
|
|
|
|
Metadata: a.Metadata,
|
|
|
|
}]
|
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
|
|
|
s, ok2 := bw.connSt[result.SubConn]
|
2019-07-30 00:19:40 +02:00
|
|
|
if !ok1 || !ok2 {
|
|
|
|
// This can only happen due to a race where Get() returned an address
|
|
|
|
// that was subsequently removed by Notify. In this case we should
|
|
|
|
// retry always.
|
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
|
|
|
return balancer.PickResult{}, balancer.ErrNoSubConnAvailable
|
2019-07-30 00:19:40 +02:00
|
|
|
}
|
|
|
|
switch s.s {
|
|
|
|
case connectivity.Ready, connectivity.Idle:
|
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
|
|
|
return result, nil
|
2019-07-30 00:19:40 +02:00
|
|
|
case connectivity.Shutdown, connectivity.TransientFailure:
|
|
|
|
// If the returned sc has been shut down or is in transient failure,
|
|
|
|
// return error, and this RPC will fail or wait for another picker (if
|
|
|
|
// non-failfast).
|
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
|
|
|
return balancer.PickResult{}, balancer.ErrTransientFailure
|
2019-07-30 00:19:40 +02:00
|
|
|
default:
|
|
|
|
// For other states (connecting or unknown), the v1 balancer would
|
|
|
|
// traditionally wait until ready and then issue the RPC. Returning
|
|
|
|
// ErrNoSubConnAvailable will be a slight improvement in that it will
|
|
|
|
// allow the balancer to choose another address in case others are
|
|
|
|
// connected.
|
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
|
|
|
return balancer.PickResult{}, balancer.ErrNoSubConnAvailable
|
2018-09-24 18:30:39 +02:00
|
|
|
}
|
|
|
|
}
|