forked from servicemeshinterface/smi-controller-sdk
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathspecs.feature
More file actions
161 lines (150 loc) · 3.87 KB
/
specs.feature
File metadata and controls
161 lines (150 loc) · 3.87 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
Feature: specs.smi-spec.io
In order to test the specs.smi-spec.io CRDs
As a developer
I need to ensure the specification is accepted by the server
@specs @HTTPRouteGroup
Scenario: Apply alpha1 HTTPRouteGroup
Given the server is running
When I create the following resource
```
apiVersion: specs.smi-spec.io/v1alpha1
kind: HTTPRouteGroup
metadata:
name: the-routes
matches:
- name: metrics
pathRegex: "/metrics"
methods:
- GET
- name: health
pathRegex: "/ping"
methods: ["*"]
```
Then I expect "UpsertHTTPRouteGroup" to be called 1 time
@specs @HTTPRouteGroup
Scenario: Apply alpha2 HTTPRouteGroup
Given the server is running
When I create the following resource
```
apiVersion: specs.smi-spec.io/v1alpha2
kind: HTTPRouteGroup
metadata:
name: the-routes
matches:
- name: metrics
pathRegex: "/metrics"
methods:
- GET
- name: health
pathRegex: "/ping"
methods: ["*"]
```
Then I expect "UpsertHTTPRouteGroup" to be called 1 time
@specs @HTTPRouteGroup
Scenario: Apply alpha3 HTTPRouteGroup
Given the server is running
When I create the following resource
```
apiVersion: specs.smi-spec.io/v1alpha3
kind: HTTPRouteGroup
metadata:
name: the-routes
spec:
matches:
- name: metrics
pathRegex: "/metrics"
methods:
- GET
- name: health
pathRegex: "/ping"
methods: ["*"]
```
Then I expect "UpsertHTTPRouteGroup" to be called 1 time
@specs @HTTPRouteGroup
Scenario: Apply alpha4 HTTPRouteGroup
Given the server is running
When I create the following resource
```
apiVersion: specs.smi-spec.io/v1alpha4
kind: HTTPRouteGroup
metadata:
name: the-routes
spec:
matches:
- name: metrics
pathRegex: "/metrics"
methods:
- GET
headers:
x-debug: "1"
- name: health
pathRegex: "/ping"
methods: ["*"]
```
Then I expect "UpsertHTTPRouteGroup" to be called 1 time
@specs @TPCRoute
Scenario: Apply alpha1 TCPRoute
Given the server is running
When I create the following resource
```
apiVersion: specs.smi-spec.io/v1alpha1
kind: TCPRoute
metadata:
name: tcp-route
```
Then I expect "UpsertTCPRoute" to be called 1 time
@specs @TPCRoute
Scenario: Apply alpha2 TCPRoute
Given the server is running
When I create the following resource
```
apiVersion: specs.smi-spec.io/v1alpha2
kind: TCPRoute
metadata:
name: tcp-route
```
Then I expect "UpsertTCPRoute" to be called 1 time
@specs @TPCRoute
Scenario: Apply alpha3 TCPRoute
Given the server is running
When I create the following resource
```
apiVersion: specs.smi-spec.io/v1alpha3
kind: TCPRoute
metadata:
name: tcp-route
spec: {}
```
Then I expect "UpsertTCPRoute" to be called 1 time
@specs @TPCRoute
Scenario: Apply alpha4 TCPRoute
Given the server is running
When I create the following resource
```
apiVersion: specs.smi-spec.io/v1alpha4
kind: TCPRoute
metadata:
name: the-routes
spec:
matches:
ports:
- 3306
- 6446
```
Then I expect "UpsertTCPRoute" to be called 1 time
@specs @UDPRoute
Scenario: Apply alpha4 UDPRoute
Given the server is running
When I create the following resource
```
apiVersion: specs.smi-spec.io/v1alpha4
kind: UDPRoute
metadata:
name: the-routes
spec:
matches:
ports:
- 989
- 990
```
Then I expect "UpsertUDPRoute" to be called 1 time