mirror of
https://github.com/status-im/consul.git
synced 2025-01-17 09:11:28 +00:00
f65f001675
In some circumstances a consul 1.4 client could be running in an un-upgraded 1.3 or lower cluster. Currently this gives a 500 error on the new ACL token endpoint. Here we catch this specific 500 error/message and set the users AccessorID to null. Elsewhere in the frontend we use this fact (AccessorID being null) to decide whether to present the legacy or the new ACL UI to the user. Also: - Re-adds in most of the old style ACL acceptance tests, now that we are keeping the old style UI - Restricts code editors to HCL only mode for all `Rules` editing (legacy/'half legacy'/new style) - Adds a [Stop using] button to the old style ACL rows so its possible to logout. - Updates copy and documentation links for the upgrade notices
43 lines
1.1 KiB
Gherkin
43 lines
1.1 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / acls / tokens / index: ACL Token List
|
|
|
|
Scenario: I see the tokens
|
|
Given 1 datacenter model with the value "dc-1"
|
|
And 3 token models
|
|
When I visit the tokens page for yaml
|
|
---
|
|
dc: dc-1
|
|
---
|
|
Then the url should be /dc-1/acls/tokens
|
|
Then I see 3 token models
|
|
Scenario: I see the legacy message if I have one legacy token
|
|
Given 1 datacenter model with the value "dc-1"
|
|
And 3 token models from yaml
|
|
---
|
|
- Legacy: true
|
|
- Legacy: false
|
|
- Legacy: false
|
|
---
|
|
When I visit the tokens page for yaml
|
|
---
|
|
dc: dc-1
|
|
---
|
|
Then the url should be /dc-1/acls/tokens
|
|
And I see update
|
|
And I see 3 token models
|
|
Scenario: I don't see the legacy message if I have no legacy tokens
|
|
Given 1 datacenter model with the value "dc-1"
|
|
And 3 token models from yaml
|
|
---
|
|
- Legacy: false
|
|
- Legacy: false
|
|
- Legacy: false
|
|
---
|
|
When I visit the tokens page for yaml
|
|
---
|
|
dc: dc-1
|
|
---
|
|
Then the url should be /dc-1/acls/tokens
|
|
And I don't see update
|
|
And I see 3 token models
|