Skip to content

Commit 5f4b128

Browse files
api-clients-generation-pipeline[bot]ci.datadog-api-spec
api-clients-generation-pipeline[bot]
and
ci.datadog-api-spec
authored
Update CODEOWNERS (#2550)
Co-authored-by: ci.datadog-api-spec <[email protected]>
1 parent c524af3 commit 5f4b128

File tree

3 files changed

+25
-25
lines changed

3 files changed

+25
-25
lines changed

‎.apigentools-info

+4-4
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
"spec_versions": {
55
"v1": {
66
"apigentools_version": "1.6.6",
7-
"regenerated": "2025-05-02 09:33:50.409735",
8-
"spec_repo_commit": "77cf469a"
7+
"regenerated": "2025-05-06 15:06:00.944093",
8+
"spec_repo_commit": "d0ee626b"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2025-05-02 09:33:50.425418",
13-
"spec_repo_commit": "77cf469a"
12+
"regenerated": "2025-05-06 15:06:00.959289",
13+
"spec_repo_commit": "d0ee626b"
1414
}
1515
}
1616
}

‎tests/v1/features/metrics.feature

+16-16
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Feature: Metrics
1414
Given a valid "apiKeyAuth" key in the system
1515
And an instance of "Metrics" API
1616

17-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
17+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
1818
Scenario: Edit metric metadata returns "Bad Request" response
1919
Given a valid "appKeyAuth" key in the system
2020
And new "UpdateMetricMetadata" request
@@ -23,7 +23,7 @@ Feature: Metrics
2323
When the request is sent
2424
Then the response status is 400 Bad Request
2525

26-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
26+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
2727
Scenario: Edit metric metadata returns "Not Found" response
2828
Given a valid "appKeyAuth" key in the system
2929
And new "UpdateMetricMetadata" request
@@ -32,7 +32,7 @@ Feature: Metrics
3232
When the request is sent
3333
Then the response status is 404 Not Found
3434

35-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
35+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
3636
Scenario: Edit metric metadata returns "OK" response
3737
Given a valid "appKeyAuth" key in the system
3838
And new "UpdateMetricMetadata" request
@@ -41,39 +41,39 @@ Feature: Metrics
4141
When the request is sent
4242
Then the response status is 200 OK
4343

44-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
44+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
4545
Scenario: Get active metrics list returns "Bad Request" response
4646
Given a valid "appKeyAuth" key in the system
4747
And new "ListActiveMetrics" request
4848
And request contains "from" parameter from "REPLACE.ME"
4949
When the request is sent
5050
Then the response status is 400 Bad Request
5151

52-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
52+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
5353
Scenario: Get active metrics list returns "OK" response
5454
Given a valid "appKeyAuth" key in the system
5555
And new "ListActiveMetrics" request
5656
And request contains "from" parameter from "REPLACE.ME"
5757
When the request is sent
5858
Then the response status is 200 OK
5959

60-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
60+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
6161
Scenario: Get metric metadata returns "Not Found" response
6262
Given a valid "appKeyAuth" key in the system
6363
And new "GetMetricMetadata" request
6464
And request contains "metric_name" parameter from "REPLACE.ME"
6565
When the request is sent
6666
Then the response status is 404 Not Found
6767

68-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
68+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
6969
Scenario: Get metric metadata returns "OK" response
7070
Given a valid "appKeyAuth" key in the system
7171
And new "GetMetricMetadata" request
7272
And request contains "metric_name" parameter from "REPLACE.ME"
7373
When the request is sent
7474
Then the response status is 200 OK
7575

76-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
76+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
7777
Scenario: Query timeseries points returns "Bad Request" response
7878
Given a valid "appKeyAuth" key in the system
7979
And new "QueryMetrics" request
@@ -83,7 +83,7 @@ Feature: Metrics
8383
When the request is sent
8484
Then the response status is 400 Bad Request
8585

86-
@team:DataDog/metrics-intake @team:DataDog/metrics-query
86+
@team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
8787
Scenario: Query timeseries points returns "OK" response
8888
Given a valid "appKeyAuth" key in the system
8989
And new "QueryMetrics" request
@@ -95,15 +95,15 @@ Feature: Metrics
9595
And the response "status" is equal to "ok"
9696
And the response "query" is equal to "system.cpu.idle{*}"
9797

98-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
98+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
9999
Scenario: Search metrics returns "Bad Request" response
100100
Given a valid "appKeyAuth" key in the system
101101
And new "ListMetrics" request
102102
And request contains "q" parameter from "REPLACE.ME"
103103
When the request is sent
104104
Then the response status is 400 Bad Request
105105

106-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
106+
@generated @skip @team:DataDog/metrics-experience @team:DataDog/metrics-index @team:DataDog/metrics-intake @team:DataDog/timeseries-query
107107
Scenario: Search metrics returns "OK" response
108108
Given a valid "appKeyAuth" key in the system
109109
And new "ListMetrics" request
@@ -119,7 +119,7 @@ Feature: Metrics
119119
When the request is sent
120120
Then the response status is 202 Payload accepted
121121

122-
@integration-only @skip-terraform-config @skip-validation @team:DataDog/metrics-intake @team:DataDog/metrics-query
122+
@integration-only @skip-terraform-config @skip-validation @team:DataDog/metrics-intake
123123
Scenario: Submit deflate metrics returns "Payload accepted" response
124124
Given new "SubmitMetrics" request
125125
And body with value {"series": [{"metric": "system.load.1", "type": "gauge", "points": [[{{ timestamp("now") }}, 1.1]], "tags": ["test:{{ unique_alnum }}"]}]}
@@ -155,28 +155,28 @@ Feature: Metrics
155155
When the request is sent
156156
Then the response status is 408 Request timeout
157157

158-
@skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
158+
@skip @team:DataDog/metrics-intake
159159
Scenario: Submit metrics returns "Bad Request" response
160160
Given new "SubmitMetrics" request
161161
And body with value "invalid"
162162
When the request is sent
163163
Then the response status is 400 Bad Request
164164

165-
@skip-validation @team:DataDog/metrics-intake @team:DataDog/metrics-query
165+
@skip-validation @team:DataDog/metrics-intake
166166
Scenario: Submit metrics returns "Payload accepted" response
167167
Given new "SubmitMetrics" request
168168
And body with value {"series": [{"metric": "system.load.1", "type": "gauge", "points": [[{{ timestamp("now") }}, 1.1]], "tags": ["test:{{ unique_alnum }}"]}]}
169169
When the request is sent
170170
Then the response status is 202 Payload accepted
171171

172-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
172+
@generated @skip @team:DataDog/metrics-intake
173173
Scenario: Submit metrics returns "Payload too large" response
174174
Given new "SubmitMetrics" request
175175
And body with value {"series": [{"metric": "system.load.1", "points": [[1475317847.0, 0.7]]}]}
176176
When the request is sent
177177
Then the response status is 413 Payload too large
178178

179-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
179+
@generated @skip @team:DataDog/metrics-intake
180180
Scenario: Submit metrics returns "Request timeout" response
181181
Given new "SubmitMetrics" request
182182
And body with value {"series": [{"metric": "system.load.1", "points": [[1475317847.0, 0.7]]}]}

‎tests/v2/features/metrics.feature

+5-5
Original file line numberDiff line numberDiff line change
@@ -320,36 +320,36 @@ Feature: Metrics
320320
And the response "data.type" is equal to "scalar_response"
321321
And the response "data.attributes.columns[0].name" is equal to "a"
322322

323-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
323+
@generated @skip @team:DataDog/metrics-intake
324324
Scenario: Submit metrics returns "Bad Request" response
325325
Given new "SubmitMetrics" request
326326
And body with value {"series": [{"metric": "system.load.1", "points": [{"timestamp": 1475317847, "value": 0.7}], "resources": [{"name": "dummyhost", "type": "host"}]}]}
327327
When the request is sent
328328
Then the response status is 400 Bad Request
329329

330-
@team:DataDog/metrics-intake @team:DataDog/metrics-query
330+
@team:DataDog/metrics-intake
331331
Scenario: Submit metrics returns "Payload accepted" response
332332
Given new "SubmitMetrics" request
333333
And body with value {"series": [{"metric": "system.load.1", "type": 0, "points": [{"timestamp": {{ timestamp('now') }}, "value": 0.7}], "resources": [{"name": "dummyhost", "type": "host"}]}]}
334334
When the request is sent
335335
Then the response status is 202 Payload accepted
336336
And the response "errors" has length 0
337337

338-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
338+
@generated @skip @team:DataDog/metrics-intake
339339
Scenario: Submit metrics returns "Payload too large" response
340340
Given new "SubmitMetrics" request
341341
And body with value {"series": [{"metric": "system.load.1", "points": [{"timestamp": 1475317847, "value": 0.7}], "resources": [{"name": "dummyhost", "type": "host"}]}]}
342342
When the request is sent
343343
Then the response status is 413 Payload too large
344344

345-
@generated @skip @team:DataDog/metrics-intake @team:DataDog/metrics-query
345+
@generated @skip @team:DataDog/metrics-intake
346346
Scenario: Submit metrics returns "Request timeout" response
347347
Given new "SubmitMetrics" request
348348
And body with value {"series": [{"metric": "system.load.1", "points": [{"timestamp": 1475317847, "value": 0.7}], "resources": [{"name": "dummyhost", "type": "host"}]}]}
349349
When the request is sent
350350
Then the response status is 408 Request timeout
351351

352-
@integration-only @skip-terraform-config @skip-validation @team:DataDog/metrics-intake @team:DataDog/metrics-query
352+
@integration-only @skip-terraform-config @skip-validation @team:DataDog/metrics-intake
353353
Scenario: Submit metrics with compression returns "Payload accepted" response
354354
Given new "SubmitMetrics" request
355355
And body with value {"series": [{"metric": "system.load.1", "type": 0, "points": [{"timestamp": {{ timestamp('now') }}, "value": 0.7}]}]}

0 commit comments

Comments
 (0)