consul/ui-v2/tests/acceptance/dc
John Cowen 2838f7a2e9
ui: Reduce discovery-chain log errors (#8065)
* ui: Reduce discovery-chain log spam

Currently the only way that the UI can know whether connect is enabled
or not is whether we get 500 errors from certain endpoints.

One of these endpoints we already use, so aswell as recovering from a
500 error, we also remember that connect is disabled for the rest of the
page 'session' (so until the page is refreshed), and make no further
http requests to the endpoint for that specific datacenter.

This means that log spam is reduced to only 1 log per page refresh/dc
instead of 1 log per service navigation.

Longer term we'll need some way to dynamically discover whether connect
is enabled per datacenter without relying on something that will add
error logs to consul.
2020-06-10 16:07:06 +01:00
..
acls UI: Improved Login/Logout flow inc SSO support (#7790) 2020-05-12 17:14:51 +00:00
intentions ui: Per Service Intentions Tab (#7615) 2020-05-12 17:14:26 +00:00
kvs ui: Reduce discovery-chain log errors (#8065) 2020-06-10 16:07:06 +01:00
nodes ui: Test Improvements (#7854) 2020-05-12 17:14:57 +00:00
nspaces ui: Redesign - Service List page with Gateways (#7781) 2020-05-12 17:14:42 +00:00
services ui: Reduce discovery-chain log errors (#8065) 2020-06-10 16:07:06 +01:00
error.feature UI: Improved Login/Logout flow inc SSO support (#7790) 2020-05-12 17:14:51 +00:00
forwarding.feature ui: Acceptance test improvements to prepare for more NS tests (#6980) 2020-01-24 12:26:28 +00:00
index.feature ui: Acceptance test improvements to prepare for more NS tests (#6980) 2020-01-24 12:26:28 +00:00
list-blocking.feature ui: Redesign - Service Detail Page (#7655) 2020-05-12 17:14:27 +00:00
list.feature ui: Redesign Service List page (#7605) 2020-05-12 17:14:25 +00:00