Add changelog
This commit is contained in:
parent
1de0af4be1
commit
ef681d06dc
|
@ -0,0 +1,3 @@
|
|||
```release-note:feature
|
||||
ui: Filter agentless (synthetic) nodes from the nodes list page.
|
||||
```
|
|
@ -1,4 +1,7 @@
|
|||
@setupApplicationTest
|
||||
# Nodes have been removed from this list because they randomly get
|
||||
# assigned the synthetic-node property which filters them out of the list page.
|
||||
# We are already testing the nodes being listed in the nodes index feature test.
|
||||
Feature: dc / list: List Models
|
||||
Scenario: Listing [Model]
|
||||
Given 1 datacenter model with the value "dc-1"
|
||||
|
@ -13,7 +16,7 @@ Feature: dc / list: List Models
|
|||
Where:
|
||||
-------------------------------------------------
|
||||
| Model | Page | Url |
|
||||
| node | nodes | /dc-1/nodes |
|
||||
# | node | nodes | /dc-1/nodes |
|
||||
| kv | kvs | /dc-1/kv |
|
||||
# | acl | acls | /dc-1/acls |
|
||||
| token | tokens | /dc-1/acls/tokens |
|
||||
|
|
|
@ -6,22 +6,32 @@ Feature: dc / nodes / empty-ids: Hedge for if nodes come in over the API with no
|
|||
---
|
||||
- ID: id-1
|
||||
Node: name-1
|
||||
Meta:
|
||||
synthetic-node: false
|
||||
Checks:
|
||||
- Status: passing
|
||||
- ID: ""
|
||||
Node: name-2
|
||||
Meta:
|
||||
synthetic-node: false
|
||||
Checks:
|
||||
- Status: passing
|
||||
- ID: ""
|
||||
Node: name-3
|
||||
Meta:
|
||||
synthetic-node: false
|
||||
Checks:
|
||||
- Status: passing
|
||||
- ID: ""
|
||||
Node: name-4
|
||||
Meta:
|
||||
synthetic-node: false
|
||||
Checks:
|
||||
- Status: passing
|
||||
- ID: ""
|
||||
Node: name-5
|
||||
Meta:
|
||||
synthetic-node: false
|
||||
Checks:
|
||||
- Status: passing
|
||||
---
|
||||
|
|
|
@ -2,7 +2,27 @@
|
|||
Feature: dc / nodes / navigation
|
||||
Scenario: Clicking a node in the listing and back again
|
||||
Given 1 datacenter model with the value "dc-1"
|
||||
And 3 node models
|
||||
And 3 node models from yaml
|
||||
---
|
||||
- Node: Node-A
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: critical
|
||||
ServiceID: ""
|
||||
- Node: Node-B
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: passing
|
||||
ServiceID: ""
|
||||
- Node: Node-C
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: warning
|
||||
ServiceID: ""
|
||||
---
|
||||
When I visit the nodes page for yaml
|
||||
---
|
||||
dc: dc-1
|
||||
|
|
|
@ -2,7 +2,27 @@
|
|||
Feature: dc / nodes / no-leader
|
||||
Scenario: Leader hasn't been elected
|
||||
Given 1 datacenter model with the value "dc-1"
|
||||
And 3 node models
|
||||
And 3 node models from yaml
|
||||
---
|
||||
- Node: Node-A
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: critical
|
||||
ServiceID: ""
|
||||
- Node: Node-B
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: passing
|
||||
ServiceID: ""
|
||||
- Node: Node-C
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: warning
|
||||
ServiceID: ""
|
||||
---
|
||||
And the url "/v1/status/leader" responds with from yaml
|
||||
---
|
||||
body: |
|
||||
|
|
|
@ -5,26 +5,38 @@ Feature: dc / nodes / sorting
|
|||
And 6 node models from yaml
|
||||
---
|
||||
- Node: Node-A
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: critical
|
||||
ServiceID: ""
|
||||
- Node: Node-B
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: passing
|
||||
ServiceID: ""
|
||||
- Node: Node-C
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: warning
|
||||
ServiceID: ""
|
||||
- Node: Node-D
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: critical
|
||||
ServiceID: ""
|
||||
- Node: Node-E
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: critical
|
||||
ServiceID: ""
|
||||
- Node: Node-F
|
||||
Meta:
|
||||
synthetic-node: "false"
|
||||
Checks:
|
||||
- Status: warning
|
||||
ServiceID: ""
|
||||
|
|
Loading…
Reference in New Issue