mirror of
https://github.com/status-im/consul.git
synced 2025-02-06 10:54:11 +00:00
fc14a412fd
* Add Partition to all our models * Add partitions into our serializers/fingerprinting * Make some amends to a few adapters ready for partitions * Amend blueprints to avoid linting error * Update all our repositories to include partitions, also Remove enabled/disable nspace repo and just use a nspace with conditionals * Ensure nspace and parition parameters always return '' no matter what * Ensure data-sink finds the model properly This will later be replaced by a @dataSink decorator but we are find kicking that can down the road a little more * Add all the new partition data layer * Add a way to set the title of the page from inside the route and make it accessibile via a route announcer * Make the Consul Route the default/basic one * Tweak nspace and partition abilities not to check the length * Thread partition through all the components that need it * Some ACL tweaks * Move the entire app to use partitions * Delete all the tests we no longer need * Update some Unit tests to use partition * Fix up KV title tests * Fix up a few more acceptance tests * Fixup and temporarily ignore some acceptance tests * Stop using ember-cli-page-objects fillable as it doesn't seem to work * Fix lint error * Remove old ACL related test * Add a tick after filling out forms * Fix token warning modal * Found some more places where we need a partition var * Fixup some more acceptance tests * Tokens still needs a repo service for CRUD * Remove acceptance tests we no longer need * Fixup and "FIXME ignore" a few tests * Remove an s * Disable blocking queries for KV to revert to previous release for now * Fixup adapter tests to follow async/function resolving interface * Fixup all the serializer integration tests * Fixup service/repo integration tests * Fixup deleting acceptance test * Fixup some ent tests * Make sure nspaces passes the dc through for when thats important * ...aaaand acceptance nspaces with the extra dc param
52 lines
1.7 KiB
Gherkin
52 lines
1.7 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / kvs / create
|
|
Scenario: Creating a root KV
|
|
Given 1 datacenter model with the value "datacenter"
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
---
|
|
Then the url should be /datacenter/kv/create
|
|
And the title should be "New Key / Value - Consul"
|
|
Then I fill in with yaml
|
|
---
|
|
additional: key-value
|
|
value: value
|
|
---
|
|
And I submit
|
|
Then the url should be /datacenter/kv
|
|
Then a PUT request was made to "/v1/kv/key-value?dc=datacenter&ns=@namespace"
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Scenario: Creating a folder
|
|
Given 1 datacenter model with the value "datacenter"
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
---
|
|
Then the url should be /datacenter/kv/create
|
|
And the title should be "New Key / Value - Consul"
|
|
Then I fill in with yaml
|
|
---
|
|
additional: key-value/
|
|
---
|
|
And I submit
|
|
Then the url should be /datacenter/kv
|
|
Then a PUT request was made to "/v1/kv/key-value/?dc=datacenter&ns=@namespace"
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Scenario: Clicking create from within a folder
|
|
Given 1 datacenter model with the value "datacenter"
|
|
And 1 kv model from yaml
|
|
---
|
|
- key-value/
|
|
---
|
|
When I visit the kvs page for yaml
|
|
---
|
|
dc: datacenter
|
|
---
|
|
And I click kv on the kvs
|
|
And I click create
|
|
And I see the text "New Key / Value" in "h1"
|
|
And I see the text "key-value" in "[data-test-breadcrumbs] li:nth-child(2) a"
|