consul/ui-v2/tests/acceptance/dc/acls/tokens/legacy/update.feature

57 lines
1.8 KiB
Gherkin
Raw Normal View History

@setupApplicationTest
Feature: dc / acls / tokens / legacy / update: ACL Token Update
Background:
Given 1 datacenter model with the value "datacenter"
And 1 token model from yaml
---
AccessorID: key
SecretID: secret
Rules: ''
Type: client
Policies: ~
---
When I visit the token page for yaml
---
dc: datacenter
token: key
---
Then the url should be /datacenter/acls/tokens/key
Scenario: Update to [Name]
Then I fill in with yaml
---
name: [Name]
---
# TODO: Remove this when I'm 100% sure token types are gone
# And I click "[value=[Type]]"
And I submit
Then a PUT request is made to "/v1/acl/update?dc=datacenter" with the body from yaml
# You can no longer edit Type but make sure it gets sent
---
ID: secret
Name: [Name]
Type: client
---
Then the url should be /datacenter/acls/tokens
And "[data-notification]" has the "notification-update" class
And "[data-notification]" has the "success" class
Where:
---------------------------------------------
| Name | Rules |
| key-name | node "0" {policy = "read"} |
| key name | node "0" {policy = "write"} |
| key%20name | node "0" {policy = "read"} |
| utf8? | node "0" {policy = "write"} |
---------------------------------------------
Scenario: There was an error saving the key
Given the url "/v1/acl/update" responds with a 500 status
And I submit
Then the url should be /datacenter/acls/tokens/key
Then "[data-notification]" has the "notification-update" class
And "[data-notification]" has the "error" class
# @ignore
# Scenario: Rules can be edited/updated
# Then ok
# @ignore
# Scenario: The feedback dialog says success or failure
# Then ok