mirror of
https://github.com/status-im/consul.git
synced 2025-01-10 05:45:46 +00:00
e8722e6a35
* ui: Normal proxies line to services, sidecars to instances Following on from https://github.com/hashicorp/consul/pull/5933 we noticed that 'normal' proxies should link to the service, rather than the service instance. Additionally proxy 'searching' within the repository should take into account the name of the node that the originating service is on (sidecar proxies are generally co-located) Added an additional test here to prove that a sidecar-proxy with the same service id but on a different node does not show the sidecar proxy link.
17 lines
548 B
Gherkin
17 lines
548 B
Gherkin
@setupApplicationTest
|
|
Feature: dc / services / instances / error: Visit Service Instance what doesn't exist
|
|
Scenario: No instance can be found in the API response
|
|
Given 1 datacenter model with the value "dc1"
|
|
And 1 instance model
|
|
When I visit the instance page for yaml
|
|
---
|
|
dc: dc1
|
|
service: service-0
|
|
node: node-0
|
|
id: id-that-doesnt-exist
|
|
---
|
|
Then the url should be /dc1/services/service-0/node-0/id-that-doesnt-exist
|
|
And I see the text "404 (Unable to find instance)" in "[data-test-error]"
|
|
|
|
|