d1b3a63b2f
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
40 lines
794 B
Gherkin
40 lines
794 B
Gherkin
@setupApplicationTest
|
|
Feature: dc / acls / list-order
|
|
In order to be able to find ACL tokens easier
|
|
As a user
|
|
I want to see the ACL listed alphabetically by Name
|
|
|
|
Scenario: I have 10 randomly sorted tokens
|
|
Given 1 datacenter model with the value "datacenter"
|
|
And I'm using a legacy token
|
|
And 10 acl model from yaml
|
|
---
|
|
- Name: zz
|
|
- Name: 123
|
|
- Name: aa
|
|
- Name: 9857
|
|
- Name: sfgr
|
|
- Name: foo
|
|
- Name: bar
|
|
- Name: xft
|
|
- Name: z-35y
|
|
- Name: __acl
|
|
---
|
|
When I visit the acls page for yaml
|
|
---
|
|
dc: datacenter
|
|
---
|
|
Then I see name on the acls like yaml
|
|
---
|
|
- __acl
|
|
- 123
|
|
- 9857
|
|
- aa
|
|
- bar
|
|
- foo
|
|
- sfgr
|
|
- xft
|
|
- z-35y
|
|
- zz
|
|
---
|