2018-10-19 15:17:02 +00:00
|
|
|
@setupApplicationTest
|
|
|
|
|
Feature: dc / acls / tokens / use: Using an ACL token
|
|
|
|
|
Background:
|
|
|
|
|
Given 1 datacenter model with the value "datacenter"
|
|
|
|
|
And 1 token model from yaml
|
|
|
|
|
---
|
|
|
|
|
AccessorID: token
|
|
|
|
|
SecretID: ee52203d-989f-4f7a-ab5a-2bef004164ca
|
ui: Adds Partitions to the HTTP layer (#10447)
This PR mainly adds partition to our HTTP adapter. Additionally and perhaps most importantly, we've also taken the opportunity to move our 'conditional namespaces' deeper into the app.
The reason for doing this was, we like that namespaces should be thought of as required instead of conditional, 'special' things and would like the same thinking to be applied to partitions.
Now, instead of using code throughout the app throughout the adapters to add/remove namespaces or partitions depending on whether they are enabled or not. As a UI engineer you just pretend that namespaces and partitions are always enabled, and we remove them for you deeper in the app, out of the way of you forgetting to treat these properties as a special case.
Notes:
Added a PartitionAbility while we were there (not used as yet)
Started to remove the CONSTANT variables we had just for property names. I prefer that our adapters are as readable and straightforwards as possible, it just looks like HTTP.
We'll probably remove our formatDatacenter method we use also at some point, it was mainly too make it look the same as our previous formatNspace, but now we don't have that, it instead now looks different!
We enable parsing of partition in the UIs URL, but this is feature flagged so still does nothing just yet.
All of the test changes were related to the fact that we were treating client.url as a function rather than a method, and now that we reference this in client.url (etc) it needs binding to client.
2021-09-15 17:09:55 +00:00
|
|
|
Namespace: @!namespace
|
2018-10-19 15:17:02 +00:00
|
|
|
---
|
2020-04-08 17:03:18 +00:00
|
|
|
And settings from yaml
|
|
|
|
|
---
|
|
|
|
|
consul:token:
|
|
|
|
|
SecretID: secret
|
|
|
|
|
AccessorID: accessor
|
|
|
|
|
Namespace: default
|
|
|
|
|
---
|
2018-10-19 15:17:02 +00:00
|
|
|
Scenario: Using an ACL token from the listing page
|
|
|
|
|
When I visit the tokens page for yaml
|
|
|
|
|
---
|
|
|
|
|
dc: datacenter
|
|
|
|
|
---
|
|
|
|
|
And I click actions on the tokens
|
|
|
|
|
And I click use on the tokens
|
|
|
|
|
And I click confirmUse on the tokens
|
|
|
|
|
Then "[data-notification]" has the "notification-use" class
|
|
|
|
|
And "[data-notification]" has the "success" class
|
|
|
|
|
Then I have settings like yaml
|
|
|
|
|
---
|
2020-01-24 12:26:28 +00:00
|
|
|
consul:token: "{\"AccessorID\":\"token\",\"SecretID\":\"ee52203d-989f-4f7a-ab5a-2bef004164ca\",\"Namespace\":\"@namespace\"}"
|
2018-10-19 15:17:02 +00:00
|
|
|
---
|
|
|
|
|
Scenario: Using an ACL token from the detail page
|
|
|
|
|
When I visit the token page for yaml
|
|
|
|
|
---
|
|
|
|
|
dc: datacenter
|
|
|
|
|
token: token
|
|
|
|
|
---
|
|
|
|
|
And I click use
|
|
|
|
|
And I click confirmUse
|
|
|
|
|
Then "[data-notification]" has the "notification-use" class
|
|
|
|
|
And "[data-notification]" has the "success" class
|
|
|
|
|
Then I have settings like yaml
|
|
|
|
|
---
|
2020-01-24 12:26:28 +00:00
|
|
|
consul:token: "{\"AccessorID\":\"token\",\"SecretID\":\"ee52203d-989f-4f7a-ab5a-2bef004164ca\",\"Namespace\":\"@namespace\"}"
|
2018-10-19 15:17:02 +00:00
|
|
|
---
|