6ec6530e03
In 858b05fc31 (diff-46ef88aa04507fb9b039344277531584)
we removed encoding values in pathnames as we thought they were
eventually being encoded by `ember`. It looks like this isn't the case.
Turns out sometimes they are encoded sometimes they aren't. It's complicated.
If at all possible refer to the PR https://github.com/hashicorp/consul/pull/5206.
It's related to the difference between `dynamic` routes and `wildcard` routes.
Partly related to this is a decision on whether we urlencode the slashes within service names or not. Whilst historically we haven't done this, we feel its a good time to change this behaviour, so we'll also be changing services to use dynamic routes instead of wildcard routes. So service links will then look like /ui/dc-1/services/application%2Fservice rather than /ui/dc-1/services/application/service
Here, we define our routes in a declarative format (for the moment at least JSON) outside of Router.map, and loop through this within Router.map to set all our routes using the standard this.route method. We essentially configure our Router from the outside. As this configuration is now done declaratively outside of Router.map we can also make this data available to href-to and paramsFor, allowing us to detect wildcard routes and therefore apply urlencoding/decoding.
Where I mention 'conditionally' below, this is detection is what is used for the decision.
We conditionally add url encoding to the `{{href-to}}` helper/addon. The
reasoning here is, if we are asking for a 'href/url' then whatever we
receive back should always be urlencoded. We've done this by reusing as much
code from the original `ember-href-to` addon as possible, after this
change every call to the `{{href-to}}` helper will be urlencoded.
As all links using `{{href-to}}` are now properly urlencoded. We also
need to decode them in the correct place 'on the other end', so..
We also override the default `Route.paramsFor` method to conditionally decode all
params before passing them to the `Route.model` hook.
Lastly (the revert), as we almost consistently use url params to
construct API calls, we make sure we re-encode any slugs that have been
passed in by the user/developer. The original API for the `createURL`
function was to allow you to pass values that didn't need encoding,
values that **did** need encoding, followed by query params (which again
require url encoding)
All in all this should make the entire ember app url encode/decode safe.
115 lines
3.6 KiB
Gherkin
115 lines
3.6 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / kvs / update: KV Update
|
|
Background:
|
|
Given 1 datacenter model with the value "datacenter"
|
|
Scenario: Update to [Name] change value to [Value]
|
|
And 1 kv model from yaml
|
|
---
|
|
Key: "[Name]"
|
|
---
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
kv: "[Name]"
|
|
---
|
|
Then the url should be /datacenter/kv/[EncodedName]/edit
|
|
# Turn the Code Editor off so we can fill the value easier
|
|
And I click "[name=json]"
|
|
Then I fill in with yaml
|
|
---
|
|
value: [Value]
|
|
---
|
|
And I submit
|
|
Then a PUT request is made to "/v1/kv/[EncodedName]?dc=datacenter" with the body "[Value]"
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Where:
|
|
---------------------------------------------------------
|
|
| Name | EncodedName | Value |
|
|
| key | key | value |
|
|
| #key | %23key | value |
|
|
| key-name | key-name | a value |
|
|
| key name | key%20name | a value |
|
|
| folder/key-name | folder/key-name | a value |
|
|
---------------------------------------------------------
|
|
Scenario: Update to a key change value to ' '
|
|
And 1 kv model from yaml
|
|
---
|
|
Key: key
|
|
---
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
kv: key
|
|
---
|
|
Then the url should be /datacenter/kv/key/edit
|
|
# Turn the Code Editor off so we can fill the value easier
|
|
And I click "[name=json]"
|
|
Then I fill in with yaml
|
|
---
|
|
value: ' '
|
|
---
|
|
And I submit
|
|
Then a PUT request is made to "/v1/kv/key?dc=datacenter" with the body " "
|
|
Then the url should be /datacenter/kv
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Scenario: Update to a key change value to ''
|
|
And 1 kv model from yaml
|
|
---
|
|
Key: key
|
|
---
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
kv: key
|
|
---
|
|
Then the url should be /datacenter/kv/key/edit
|
|
# Turn the Code Editor off so we can fill the value easier
|
|
And I click "[name=json]"
|
|
Then I fill in with yaml
|
|
---
|
|
value: ''
|
|
---
|
|
And I submit
|
|
Then a PUT request is made to "/v1/kv/key?dc=datacenter" with no body
|
|
Then the url should be /datacenter/kv
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Scenario: Update to a key when the value is empty
|
|
And 1 kv model from yaml
|
|
---
|
|
Key: key
|
|
Value: ~
|
|
---
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
kv: key
|
|
---
|
|
Then the url should be /datacenter/kv/key/edit
|
|
And I submit
|
|
Then a PUT request is made to "/v1/kv/key?dc=datacenter" with no body
|
|
Then the url should be /datacenter/kv
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Scenario: There was an error saving the key
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
kv: key
|
|
---
|
|
Then the url should be /datacenter/kv/key/edit
|
|
|
|
Given the url "/v1/kv/key" responds with a 500 status
|
|
And I submit
|
|
Then the url should be /datacenter/kv/key/edit
|
|
Then "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "error" class
|
|
@ignore
|
|
Scenario: KV's with spaces are saved correctly
|
|
Then ok
|
|
@ignore
|
|
Scenario: KV's with returns are saved correctly
|
|
Then ok
|