open-nomad/vendor
Mahmood Ali f5700611c0
api: target servers for allocation requests (#8897)
Allocation requests should target servers, which then can forward the
request to the appropriate clients.

Contacting clients directly is fragile and prune to failures: e.g.
clients maybe firewalled and not accessible from the API client, or have
some internal certificates not trusted by the API client.

FWIW, in contexts where we anticipate lots of traffic (e.g. logs, or
exec), the api package attempts contacting the client directly but then
fallsback to using the server. This approach seems excessive in these
simple GET/PUT requests.

Fixes #8894
2020-09-16 09:34:17 -04:00
..
cloud.google.com/go deps: Switch to Go modules for dependency management 2020-06-02 14:30:36 -05:00
github.com api: target servers for allocation requests (#8897) 2020-09-16 09:34:17 -04:00
go.opencensus.io consul/connect: update consul to match current 2020-08-24 10:48:27 -05:00
golang.org/x consul/connect: update consul to match current 2020-08-24 10:48:27 -05:00
google.golang.org consul/connect: update consul to match current 2020-08-24 10:48:27 -05:00
gopkg.in deps: Switch to Go modules for dependency management 2020-06-02 14:30:36 -05:00
honnef.co/go/tools deps: Switch to Go modules for dependency management 2020-06-02 14:30:36 -05:00
modules.txt remove direct dependency on ginkgo 2020-09-10 13:00:42 -04:00