6f2ecdec27
Since I was already fixing consul's tls handling in #2645 I decided to update consul/api and pre-emptively fix our tls handling against the newest consul/api behavior. consul/api's handling of http.Transports has improved but would have broken how we handled tls (again). This would have made for a nasty surprise the next time we updated consul/api. |
||
|---|---|---|
| .. | ||
| github.com | ||
| golang.org/x | ||
| gopkg.in | ||
| vendor.json | ||