John Cowen 5ea748005c
UI: External Source markers (#4640)
1. Addition of external source icons for services marked as such.
2. New %with-tooltip css component (wip)
3. New 'no healthcheck' icon as external sources might not have
healthchecks, also minus icon on node cards in the service detail view
4. If a service doesn't have healthchecks, we use the [Services] tabs as the
default instead of the [Health Checks] tab in the Service detail page. 
5. `css-var` helper. The idea here is that it will eventually be
replaced with pure css custom properties instead of having to use JS. It
would be nice to be able to build the css variables into the JS at build
time (you'd probably still want to specify in config which variables you
wanted available in JS), but that's possible future work.

Lastly there is probably a tiny bit more testing edits here than usual,
I noticed that there was an area where the dynamic mocking wasn't
happening, it was just using the mocks from consul-api-double, the mocks
I was 'dynamically' setting happened to be the same as the ones in
consul-api-double. I've fixed this here also but it wasn't effecting
anything until actually made certain values dynamic.
2018-09-12 20:23:39 +01:00

37 lines
767 B
Gherkin

@setupApplicationTest
Feature: dc / services: List Services
Scenario:
Given 1 datacenter model with the value "dc-1"
And 5 service models from yaml
---
- Name: Service 1
Meta:
external-source: consul
- Name: Service 2
Meta:
external-source: nomad
- Name: Service 3
Meta:
external-source: terraform
- Name: Service 4
Meta:
external-source: kubernetes
- Name: Service 5
Meta: ~
---
When I visit the services page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/services
Then I see 5 service models
And I see externalSource on the services like yaml
---
- consul
- nomad
- terraform
- kubernetes
- ~
---