consul/ui-v2/app
John Cowen 5debc74fa2 ui: Enable blocking queries by default (#6194)
-Enable blocking queries by default
-Change assertion to check for the last PUT request, not just any request for session destruction from a node page.

Since we've now turned on blocking queries by default this means that a
second GET request is made after the PUT request that we are asserting
for but before the assertion itself, this meant the assertion failed. We
double checked this by turning off blocking queries for this test using

```
And settings from yaml
---
consul:client:
  blocking: 0
---
```

which made the test pass again.

As moving forwards blocking queries will be on by default, we didn't
want to disable blocking queries for this test, so we now assert the
last PUT request specifically. This means we continue to assert that the
session has been destroyed but means we don't get into problems of
ordering of requests here
2019-09-04 08:35:14 +00:00
..
adapters
components ui: Change layout styling for healthcheckoutput, add CheckID (#6195) 2019-09-04 08:35:12 +00:00
computed
controllers ui: Enable blocking queries by default (#6194) 2019-09-04 08:35:14 +00:00
forms
helpers
initializers
instance-initializers
mixins
models
routes ui: Enable blocking queries by default (#6194) 2019-09-04 08:35:14 +00:00
routing
search/filters
serializers
services ui: Enable blocking queries by default (#6194) 2019-09-04 08:35:14 +00:00
styles ui: Change layout styling for healthcheckoutput, add CheckID (#6195) 2019-09-04 08:35:12 +00:00
templates ui: [Bugfix] - Sticky KV Sessions (#6166) 2019-09-04 08:35:13 +00:00
utils
validations
app.js
env.js
index.html
resolver.js
router.js