consul/agent/proxycfg
R.B. Boyer 9566df524e
agent: cache notifications work after error if the underlying RPC returns index=1 (#6547)
Fixes #6521

Ensure that initial failures to fetch an agent cache entry using the
notify API where the underlying RPC returns a synthetic index of 1
correctly recovers when those RPCs resume working.

The bug in the Cache.notifyBlockingQuery used to incorrectly "fix" the
index for the next query from 0 to 1 for all queries, when it should
have not done so for queries that errored.

Also fixed some things that made debugging difficult:

- config entry read/list endpoints send back QueryMeta headers
- xds event loops don't swallow the cache notification errors
2019-09-26 10:42:17 -05:00
..
manager.go connect: remove managed proxies (#6220) 2019-08-09 15:19:30 -04:00
manager_test.go Expose HTTP-based paths through Connect proxy (#6446) 2019-09-25 20:55:52 -06:00
proxycfg.go Proxy Config Manager (#4729) 2018-10-10 16:55:34 +01:00
snapshot.go Expose HTTP-based paths through Connect proxy (#6446) 2019-09-25 20:55:52 -06:00
state.go agent: cache notifications work after error if the underlying RPC returns index=1 (#6547) 2019-09-26 10:42:17 -05:00
state_test.go connect: generate the full SNI names for discovery targets in the compiler rather than in the xds package (#6340) 2019-08-19 13:03:03 -05:00
testing.go Expose HTTP-based paths through Connect proxy (#6446) 2019-09-25 20:55:52 -06:00