75d8abd562
* ui: Add forking based on service instance id existence Proxies come in 2 flavours, 'normal' and sidecar. We know when a proxy is a sidecar proxy based on whether a DestinationServiceID is set. LocalServiceAddress and LocalServicePort are only relevant for sidecar proxies. This adds template logic to show different text depending on this information. Additionally adds test around connect proxies (#5418) 1. Adds page object for the instance detail page 2. Adds further scenario steps used in the tests 3. Adds acceptance testing around the instance detail page. Services with proxies and the sidecar proxies and proxies themselves 4. Adds datacenter column for upstreams 5. Fixes bug routing bug for decision as to whether to request proxy information or not
23 lines
694 B
Gherkin
23 lines
694 B
Gherkin
@setupApplicationTest
|
|
Feature: dc / services / instances / with-sidecar: Show Service Instance with a Sidecar Proxy
|
|
Scenario: A Service instance has a Sidecar Proxy (a DestinationServiceID)
|
|
Given 1 datacenter model with the value "dc1"
|
|
And 1 proxy model from yaml
|
|
---
|
|
- ServiceProxy:
|
|
DestinationServiceID: service-1
|
|
---
|
|
When I visit the instance page for yaml
|
|
---
|
|
dc: dc1
|
|
service: service-0
|
|
id: service-0-with-id
|
|
---
|
|
Then the url should be /dc1/services/service-0/service-0-with-id
|
|
And I see type on the proxy like "sidecar-proxy"
|
|
|
|
And I see serviceChecksIsSelected on the tabs
|
|
And I don't see upstreams on the tabs
|
|
|
|
|