Skip to content

Commit 917bd6e

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 9fa25bca of spec repo
1 parent 5e17484 commit 917bd6e

File tree

96 files changed

+1864
-1864
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

96 files changed

+1864
-1864
lines changed

‎.apigentools-info‎

Lines changed: 4 additions & 4 deletions
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-02-04 14:10:05.819748",
8-
"spec_repo_commit": "4fb9047a"
7+
"regenerated": "2025-02-04 19:29:30.937270",
8+
"spec_repo_commit": "9fa25bca"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2025-02-04 14:10:05.835266",
13-
"spec_repo_commit": "4fb9047a"
12+
"regenerated": "2025-02-04 19:29:30.953098",
13+
"spec_repo_commit": "9fa25bca"
1414
}
1515
}
1616
}

‎features/v1/authentication.feature‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,12 +16,12 @@ Feature: Authentication
1616
Given an instance of "Authentication" API
1717
And new "Validate" request
1818

19-
@skip-validation @team:DataDog/credentials-management
19+
@skip-validation @team:DataDog/credentials-management @team:DataDog/web-frameworks-approvers
2020
Scenario: Validate API key returns "Forbidden" response
2121
When the request is sent
2222
Then the response status is 403 OK
2323

24-
@team:DataDog/credentials-management
24+
@team:DataDog/credentials-management @team:DataDog/web-frameworks-approvers
2525
Scenario: Validate API key returns "OK" response
2626
Given a valid "apiKeyAuth" key in the system
2727
When the request is sent

‎features/v1/aws_integration.feature‎

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -9,178 +9,178 @@ Feature: AWS Integration
99
And a valid "appKeyAuth" key in the system
1010
And an instance of "AWSIntegration" API
1111

12-
@generated @skip @team:DataDog/aws-integrations
12+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
1313
Scenario: Create an AWS integration returns "Bad Request" response
1414
Given new "CreateAWSAccount" request
1515
And body with value {"account_id": "123456789012", "account_specific_namespace_rules": {"auto_scaling": false, "opswork": false}, "cspm_resource_collection_enabled": true, "excluded_regions": ["us-east-1", "us-west-2"], "extended_resource_collection_enabled": true, "filter_tags": ["$KEY:$VALUE"], "host_tags": ["$KEY:$VALUE"], "metrics_collection_enabled": false, "resource_collection_enabled": true, "role_name": "DatadogAWSIntegrationRole"}
1616
When the request is sent
1717
Then the response status is 400 Bad Request
1818

19-
@generated @skip @team:DataDog/aws-integrations
19+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
2020
Scenario: Create an AWS integration returns "Conflict Error" response
2121
Given new "CreateAWSAccount" request
2222
And body with value {"account_id": "123456789012", "account_specific_namespace_rules": {"auto_scaling": false, "opswork": false}, "cspm_resource_collection_enabled": true, "excluded_regions": ["us-east-1", "us-west-2"], "extended_resource_collection_enabled": true, "filter_tags": ["$KEY:$VALUE"], "host_tags": ["$KEY:$VALUE"], "metrics_collection_enabled": false, "resource_collection_enabled": true, "role_name": "DatadogAWSIntegrationRole"}
2323
When the request is sent
2424
Then the response status is 409 Conflict Error
2525

26-
@team:DataDog/aws-integrations
26+
@team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
2727
Scenario: Create an AWS integration returns "OK" response
2828
Given new "CreateAWSAccount" request
2929
And body with value {"account_id": "{{ timestamp("now") }}00", "account_specific_namespace_rules": {"auto_scaling": false}, "cspm_resource_collection_enabled": true, "excluded_regions": ["us-east-1", "us-west-2"], "extended_resource_collection_enabled": true, "filter_tags": ["$KEY:$VALUE"], "host_tags": ["$KEY:$VALUE"], "metrics_collection_enabled": false, "role_name": "DatadogAWSIntegrationRole"}
3030
When the request is sent
3131
Then the response status is 200 OK
3232

33-
@generated @skip @team:DataDog/aws-integrations
33+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
3434
Scenario: Create an Amazon EventBridge source returns "Bad Request" response
3535
Given new "CreateAWSEventBridgeSource" request
3636
And body with value {"account_id": "123456789012", "create_event_bus": true, "event_generator_name": "app-alerts", "region": "us-east-1"}
3737
When the request is sent
3838
Then the response status is 400 Bad Request
3939

40-
@generated @skip @team:DataDog/aws-integrations
40+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
4141
Scenario: Create an Amazon EventBridge source returns "OK" response
4242
Given new "CreateAWSEventBridgeSource" request
4343
And body with value {"account_id": "123456789012", "create_event_bus": true, "event_generator_name": "app-alerts", "region": "us-east-1"}
4444
When the request is sent
4545
Then the response status is 200 OK
4646

47-
@generated @skip @team:DataDog/aws-integrations
47+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
4848
Scenario: Delete a tag filtering entry returns "Bad Request" response
4949
Given new "DeleteAWSTagFilter" request
5050
And body with value {"account_id": "FAKEAC0FAKEAC2FAKEAC", "namespace": "elb"}
5151
When the request is sent
5252
Then the response status is 400 Bad Request
5353

54-
@generated @skip @team:DataDog/aws-integrations
54+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
5555
Scenario: Delete a tag filtering entry returns "OK" response
5656
Given new "DeleteAWSTagFilter" request
5757
And body with value {"account_id": "FAKEAC0FAKEAC2FAKEAC", "namespace": "elb"}
5858
When the request is sent
5959
Then the response status is 200 OK
6060

61-
@generated @skip @team:DataDog/aws-integrations
61+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
6262
Scenario: Delete an AWS integration returns "Bad Request" response
6363
Given new "DeleteAWSAccount" request
6464
And body with value {"account_id": "123456789012", "role_name": "DatadogAWSIntegrationRole"}
6565
When the request is sent
6666
Then the response status is 400 Bad Request
6767

68-
@generated @skip @team:DataDog/aws-integrations
68+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
6969
Scenario: Delete an AWS integration returns "Conflict Error" response
7070
Given new "DeleteAWSAccount" request
7171
And body with value {"account_id": "123456789012", "role_name": "DatadogAWSIntegrationRole"}
7272
When the request is sent
7373
Then the response status is 409 Conflict Error
7474

75-
@team:DataDog/aws-integrations
75+
@team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
7676
Scenario: Delete an AWS integration returns "OK" response
7777
Given there is a valid "aws_account" in the system
7878
And new "DeleteAWSAccount" request
7979
And body with value {"account_id": "{{ timestamp("now") }}00", "role_name": "DatadogAWSIntegrationRole"}
8080
When the request is sent
8181
Then the response status is 200 OK
8282

83-
@generated @skip @team:DataDog/aws-integrations
83+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
8484
Scenario: Delete an Amazon EventBridge source returns "Bad Request" response
8585
Given new "DeleteAWSEventBridgeSource" request
8686
And body with value {"account_id": "123456789012", "event_generator_name": "app-alerts-zyxw3210", "region": "us-east-1"}
8787
When the request is sent
8888
Then the response status is 400 Bad Request
8989

90-
@generated @skip @team:DataDog/aws-integrations
90+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
9191
Scenario: Delete an Amazon EventBridge source returns "OK" response
9292
Given new "DeleteAWSEventBridgeSource" request
9393
And body with value {"account_id": "123456789012", "event_generator_name": "app-alerts-zyxw3210", "region": "us-east-1"}
9494
When the request is sent
9595
Then the response status is 200 OK
9696

97-
@generated @skip @team:DataDog/aws-integrations
97+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
9898
Scenario: Generate a new external ID returns "Bad Request" response
9999
Given new "CreateNewAWSExternalID" request
100100
And body with value {"account_id": "123456789012", "account_specific_namespace_rules": {"auto_scaling": false, "opswork": false}, "cspm_resource_collection_enabled": true, "excluded_regions": ["us-east-1", "us-west-2"], "extended_resource_collection_enabled": true, "filter_tags": ["$KEY:$VALUE"], "host_tags": ["$KEY:$VALUE"], "metrics_collection_enabled": false, "resource_collection_enabled": true, "role_name": "DatadogAWSIntegrationRole"}
101101
When the request is sent
102102
Then the response status is 400 Bad Request
103103

104-
@generated @skip @team:DataDog/aws-integrations
104+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
105105
Scenario: Generate a new external ID returns "OK" response
106106
Given new "CreateNewAWSExternalID" request
107107
And body with value {"account_id": "123456789012", "account_specific_namespace_rules": {"auto_scaling": false, "opswork": false}, "cspm_resource_collection_enabled": true, "excluded_regions": ["us-east-1", "us-west-2"], "extended_resource_collection_enabled": true, "filter_tags": ["$KEY:$VALUE"], "host_tags": ["$KEY:$VALUE"], "metrics_collection_enabled": false, "resource_collection_enabled": true, "role_name": "DatadogAWSIntegrationRole"}
108108
When the request is sent
109109
Then the response status is 200 OK
110110

111-
@generated @skip @team:DataDog/aws-integrations
111+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
112112
Scenario: Get all AWS tag filters returns "Bad Request" response
113113
Given new "ListAWSTagFilters" request
114114
And request contains "account_id" parameter from "REPLACE.ME"
115115
When the request is sent
116116
Then the response status is 400 Bad Request
117117

118-
@generated @skip @team:DataDog/aws-integrations
118+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
119119
Scenario: Get all AWS tag filters returns "OK" response
120120
Given new "ListAWSTagFilters" request
121121
And request contains "account_id" parameter from "REPLACE.ME"
122122
When the request is sent
123123
Then the response status is 200 OK
124124

125-
@generated @skip @team:DataDog/aws-integrations
125+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
126126
Scenario: Get all Amazon EventBridge sources returns "Bad Request" response
127127
Given new "ListAWSEventBridgeSources" request
128128
When the request is sent
129129
Then the response status is 400 Bad Request
130130

131-
@generated @skip @team:DataDog/aws-integrations
131+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
132132
Scenario: Get all Amazon EventBridge sources returns "OK" response
133133
Given new "ListAWSEventBridgeSources" request
134134
When the request is sent
135135
Then the response status is 200 OK
136136

137-
@generated @skip @team:DataDog/aws-integrations
137+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
138138
Scenario: List all AWS integrations returns "Bad Request" response
139139
Given new "ListAWSAccounts" request
140140
When the request is sent
141141
Then the response status is 400 Bad Request
142142

143-
@generated @skip @team:DataDog/aws-integrations
143+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
144144
Scenario: List all AWS integrations returns "OK" response
145145
Given new "ListAWSAccounts" request
146146
When the request is sent
147147
Then the response status is 200 OK
148148

149-
@generated @skip @team:DataDog/aws-integrations
149+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
150150
Scenario: List namespace rules returns "OK" response
151151
Given new "ListAvailableAWSNamespaces" request
152152
When the request is sent
153153
Then the response status is 200 OK
154154

155-
@generated @skip @team:DataDog/aws-integrations
155+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
156156
Scenario: Set an AWS tag filter returns "Bad Request" response
157157
Given new "CreateAWSTagFilter" request
158158
And body with value {"account_id": "123456789012", "namespace": "elb", "tag_filter_str": "prod*"}
159159
When the request is sent
160160
Then the response status is 400 Bad Request
161161

162-
@generated @skip @team:DataDog/aws-integrations
162+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
163163
Scenario: Set an AWS tag filter returns "OK" response
164164
Given new "CreateAWSTagFilter" request
165165
And body with value {"account_id": "123456789012", "namespace": "elb", "tag_filter_str": "prod*"}
166166
When the request is sent
167167
Then the response status is 200 OK
168168

169-
@generated @skip @team:DataDog/aws-integrations
169+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
170170
Scenario: Update an AWS integration returns "Bad Request" response
171171
Given new "UpdateAWSAccount" request
172172
And body with value {"account_id": "123456789012", "account_specific_namespace_rules": {"auto_scaling": false, "opswork": false}, "cspm_resource_collection_enabled": true, "excluded_regions": ["us-east-1", "us-west-2"], "extended_resource_collection_enabled": true, "filter_tags": ["$KEY:$VALUE"], "host_tags": ["$KEY:$VALUE"], "metrics_collection_enabled": false, "resource_collection_enabled": true, "role_name": "DatadogAWSIntegrationRole"}
173173
When the request is sent
174174
Then the response status is 400 Bad Request
175175

176-
@generated @skip @team:DataDog/aws-integrations
176+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
177177
Scenario: Update an AWS integration returns "Conflict Error" response
178178
Given new "UpdateAWSAccount" request
179179
And body with value {"account_id": "123456789012", "account_specific_namespace_rules": {"auto_scaling": false, "opswork": false}, "cspm_resource_collection_enabled": true, "excluded_regions": ["us-east-1", "us-west-2"], "extended_resource_collection_enabled": true, "filter_tags": ["$KEY:$VALUE"], "host_tags": ["$KEY:$VALUE"], "metrics_collection_enabled": false, "resource_collection_enabled": true, "role_name": "DatadogAWSIntegrationRole"}
180180
When the request is sent
181181
Then the response status is 409 Conflict Error
182182

183-
@team:DataDog/aws-integrations
183+
@team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
184184
Scenario: Update an AWS integration returns "OK" response
185185
Given there is a valid "aws_account" in the system
186186
And new "UpdateAWSAccount" request

‎features/v1/aws_logs_integration.feature‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,89 +10,89 @@ Feature: AWS Logs Integration
1010
And a valid "appKeyAuth" key in the system
1111
And an instance of "AWSLogsIntegration" API
1212

13-
@generated @skip @team:DataDog/aws-integrations
13+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
1414
Scenario: Add AWS Log Lambda ARN returns "Bad Request" response
1515
Given new "CreateAWSLambdaARN" request
1616
And body with value {"account_id": "1234567", "lambda_arn": "arn:aws:lambda:us-east-1:1234567:function:LogsCollectionAPITest"}
1717
When the request is sent
1818
Then the response status is 400 Bad Request
1919

20-
@generated @skip @team:DataDog/aws-integrations
20+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
2121
Scenario: Add AWS Log Lambda ARN returns "OK" response
2222
Given new "CreateAWSLambdaARN" request
2323
And body with value {"account_id": "1234567", "lambda_arn": "arn:aws:lambda:us-east-1:1234567:function:LogsCollectionAPITest"}
2424
When the request is sent
2525
Then the response status is 200 OK
2626

27-
@generated @skip @team:DataDog/aws-integrations
27+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
2828
Scenario: Check permissions for log services returns "Bad Request" response
2929
Given new "CheckAWSLogsServicesAsync" request
3030
And body with value {"account_id": "1234567", "services": ["s3", "elb", "elbv2", "cloudfront", "redshift", "lambda"]}
3131
When the request is sent
3232
Then the response status is 400 Bad Request
3333

34-
@generated @skip @team:DataDog/aws-integrations
34+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
3535
Scenario: Check permissions for log services returns "OK" response
3636
Given new "CheckAWSLogsServicesAsync" request
3737
And body with value {"account_id": "1234567", "services": ["s3", "elb", "elbv2", "cloudfront", "redshift", "lambda"]}
3838
When the request is sent
3939
Then the response status is 200 OK
4040

41-
@generated @skip @team:DataDog/aws-integrations
41+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
4242
Scenario: Check that an AWS Lambda Function exists returns "Bad Request" response
4343
Given new "CheckAWSLogsLambdaAsync" request
4444
And body with value {"account_id": "1234567", "lambda_arn": "arn:aws:lambda:us-east-1:1234567:function:LogsCollectionAPITest"}
4545
When the request is sent
4646
Then the response status is 400 Bad Request
4747

48-
@generated @skip @team:DataDog/aws-integrations
48+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
4949
Scenario: Check that an AWS Lambda Function exists returns "OK" response
5050
Given new "CheckAWSLogsLambdaAsync" request
5151
And body with value {"account_id": "1234567", "lambda_arn": "arn:aws:lambda:us-east-1:1234567:function:LogsCollectionAPITest"}
5252
When the request is sent
5353
Then the response status is 200 OK
5454

55-
@generated @skip @team:DataDog/aws-integrations
55+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
5656
Scenario: Delete an AWS Logs integration returns "Bad Request" response
5757
Given new "DeleteAWSLambdaARN" request
5858
And body with value {"account_id": "1234567", "lambda_arn": "arn:aws:lambda:us-east-1:1234567:function:LogsCollectionAPITest"}
5959
When the request is sent
6060
Then the response status is 400 Bad Request
6161

62-
@generated @skip @team:DataDog/aws-integrations
62+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
6363
Scenario: Delete an AWS Logs integration returns "OK" response
6464
Given new "DeleteAWSLambdaARN" request
6565
And body with value {"account_id": "1234567", "lambda_arn": "arn:aws:lambda:us-east-1:1234567:function:LogsCollectionAPITest"}
6666
When the request is sent
6767
Then the response status is 200 OK
6868

69-
@generated @skip @team:DataDog/aws-integrations
69+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
7070
Scenario: Enable an AWS Logs integration returns "Bad Request" response
7171
Given new "EnableAWSLogServices" request
7272
And body with value {"account_id": "1234567", "services": ["s3", "elb", "elbv2", "cloudfront", "redshift", "lambda"]}
7373
When the request is sent
7474
Then the response status is 400 Bad Request
7575

76-
@generated @skip @team:DataDog/aws-integrations
76+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
7777
Scenario: Enable an AWS Logs integration returns "OK" response
7878
Given new "EnableAWSLogServices" request
7979
And body with value {"account_id": "1234567", "services": ["s3", "elb", "elbv2", "cloudfront", "redshift", "lambda"]}
8080
When the request is sent
8181
Then the response status is 200 OK
8282

83-
@generated @skip @team:DataDog/aws-integrations
83+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
8484
Scenario: Get list of AWS log ready services returns "OK" response
8585
Given new "ListAWSLogsServices" request
8686
When the request is sent
8787
Then the response status is 200 OK
8888

89-
@generated @skip @team:DataDog/aws-integrations
89+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
9090
Scenario: List all AWS Logs integrations returns "Bad Request" response
9191
Given new "ListAWSLogsIntegrations" request
9292
When the request is sent
9393
Then the response status is 400 Bad Request
9494

95-
@generated @skip @team:DataDog/aws-integrations
95+
@generated @skip @team:DataDog/aws-integrations @team:DataDog/web-frameworks-approvers
9696
Scenario: List all AWS Logs integrations returns "OK" response
9797
Given new "ListAWSLogsIntegrations" request
9898
When the request is sent

0 commit comments

Comments
 (0)