-
Notifications
You must be signed in to change notification settings - Fork 19
Expand file tree
/
Copy pathlogs_archives.feature
More file actions
192 lines (166 loc) · 11.3 KB
/
logs_archives.feature
File metadata and controls
192 lines (166 loc) · 11.3 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
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
@endpoint(logs-archives) @endpoint(logs-archives-v2)
Feature: Logs Archives
Archives forward all the logs ingested to a cloud storage system. See the
[Archives Page](https://app.datadoghq.com/logs/pipelines/archives) for a
list of the archives currently configured in Datadog.
Background:
Given a valid "apiKeyAuth" key in the system
And a valid "appKeyAuth" key in the system
And an instance of "LogsArchives" API
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Create an archive returns "Bad Request" response
Given new "CreateLogsArchive" request
And body with value {"data": {"attributes": {"compression_method": "GZIP", "destination": {"container": "container-name", "integration": {"client_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa", "tenant_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa"}, "storage_account": "account-name", "type": "azure"}, "include_tags": false, "name": "Nginx Archive", "query": "source:nginx", "rehydration_max_scan_size_in_gb": 100, "rehydration_tags": ["team:intake", "team:app"]}, "type": "archives"}}
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Create an archive returns "OK" response
Given new "CreateLogsArchive" request
And body with value {"data": {"attributes": {"compression_method": "GZIP", "destination": {"container": "container-name", "integration": {"client_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa", "tenant_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa"}, "storage_account": "account-name", "type": "azure"}, "include_tags": false, "name": "Nginx Archive", "query": "source:nginx", "rehydration_max_scan_size_in_gb": 100, "rehydration_tags": ["team:intake", "team:app"]}, "type": "archives"}}
When the request is sent
Then the response status is 200 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Delete an archive returns "Bad Request" response
Given new "DeleteLogsArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Delete an archive returns "Not found" response
Given new "DeleteLogsArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not found
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Delete an archive returns "OK" response
Given new "DeleteLogsArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 204 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Get all archives returns "OK" response
Given new "ListLogsArchives" request
When the request is sent
Then the response status is 200 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Get an archive returns "Bad Request" response
Given new "GetLogsArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Get an archive returns "Not found" response
Given new "GetLogsArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not found
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Get an archive returns "OK" response
Given new "GetLogsArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 200 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Get archive order returns "OK" response
Given new "GetLogsArchiveOrder" request
When the request is sent
Then the response status is 200 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Grant role to an archive returns "Bad Request" response
Given new "AddReadRoleToArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Grant role to an archive returns "Not found" response
Given new "AddReadRoleToArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}
When the request is sent
Then the response status is 404 Not found
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Grant role to an archive returns "OK" response
Given new "AddReadRoleToArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}
When the request is sent
Then the response status is 204 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: List read roles for an archive returns "Bad Request" response
Given new "ListArchiveReadRoles" request
And request contains "archive_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: List read roles for an archive returns "Not found" response
Given new "ListArchiveReadRoles" request
And request contains "archive_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not found
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: List read roles for an archive returns "OK" response
Given new "ListArchiveReadRoles" request
And request contains "archive_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 200 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Revoke role from an archive returns "Bad Request" response
Given new "RemoveRoleFromArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Revoke role from an archive returns "Not found" response
Given new "RemoveRoleFromArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}
When the request is sent
Then the response status is 404 Not found
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Revoke role from an archive returns "OK" response
Given new "RemoveRoleFromArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}
When the request is sent
Then the response status is 204 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Update an archive returns "Bad Request" response
Given new "UpdateLogsArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"compression_method": "GZIP", "destination": {"container": "container-name", "integration": {"client_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa", "tenant_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa"}, "storage_account": "account-name", "type": "azure"}, "include_tags": false, "name": "Nginx Archive", "query": "source:nginx", "rehydration_max_scan_size_in_gb": 100, "rehydration_tags": ["team:intake", "team:app"]}, "type": "archives"}}
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Update an archive returns "Not found" response
Given new "UpdateLogsArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"compression_method": "GZIP", "destination": {"container": "container-name", "integration": {"client_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa", "tenant_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa"}, "storage_account": "account-name", "type": "azure"}, "include_tags": false, "name": "Nginx Archive", "query": "source:nginx", "rehydration_max_scan_size_in_gb": 100, "rehydration_tags": ["team:intake", "team:app"]}, "type": "archives"}}
When the request is sent
Then the response status is 404 Not found
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Update an archive returns "OK" response
Given new "UpdateLogsArchive" request
And request contains "archive_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"compression_method": "GZIP", "destination": {"container": "container-name", "integration": {"client_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa", "tenant_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa"}, "storage_account": "account-name", "type": "azure"}, "include_tags": false, "name": "Nginx Archive", "query": "source:nginx", "rehydration_max_scan_size_in_gb": 100, "rehydration_tags": ["team:intake", "team:app"]}, "type": "archives"}}
When the request is sent
Then the response status is 200 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Update archive order returns "Bad Request" response
Given new "UpdateLogsArchiveOrder" request
And body with value {"data": {"attributes": {"archive_ids": ["a2zcMylnM4OCHpYusxIi1g", "a2zcMylnM4OCHpYusxIi2g", "a2zcMylnM4OCHpYusxIi3g"]}, "type": "archive_order"}}
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Update archive order returns "OK" response
Given new "UpdateLogsArchiveOrder" request
And body with value {"data": {"attributes": {"archive_ids": ["a2zcMylnM4OCHpYusxIi1g", "a2zcMylnM4OCHpYusxIi2g", "a2zcMylnM4OCHpYusxIi3g"]}, "type": "archive_order"}}
When the request is sent
Then the response status is 200 OK
@generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding
Scenario: Update archive order returns "Unprocessable Entity" response
Given new "UpdateLogsArchiveOrder" request
And body with value {"data": {"attributes": {"archive_ids": ["a2zcMylnM4OCHpYusxIi1g", "a2zcMylnM4OCHpYusxIi2g", "a2zcMylnM4OCHpYusxIi3g"]}, "type": "archive_order"}}
When the request is sent
Then the response status is 422 Unprocessable Entity