Skip to content

Commit 20190e4

Browse files
api-clients-generation-pipeline[bot]ci.datadog-api-spec
andauthored
Revert skipping GCP integration tests (#352)
Co-authored-by: ci.datadog-api-spec <[email protected]>
1 parent 424d20f commit 20190e4

File tree

3 files changed

+21
-21
lines changed

3 files changed

+21
-21
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": "2024-10-25 13:05:51.926973",
8-
"spec_repo_commit": "a2f558e8"
7+
"regenerated": "2024-10-25 20:17:04.430049",
8+
"spec_repo_commit": "849ce45c"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2024-10-25 13:05:51.946255",
13-
"spec_repo_commit": "a2f558e8"
12+
"regenerated": "2024-10-25 20:17:04.448121",
13+
"spec_repo_commit": "849ce45c"
1414
}
1515
}
1616
}

tests/scenarios/features/v1/gcp_integration.feature

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Feature: GCP Integration
1717
When the request is sent
1818
Then the response status is 400 Bad Request
1919

20-
@replay-only @team:DataDog/gcp-integrations
20+
@team:DataDog/gcp-integrations
2121
Scenario: Create a GCP integration returns "OK" response
2222
Given new "CreateGCPIntegration" request
2323
And body with value {"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs", "auth_uri": "https://accounts.google.com/o/oauth2/auth", "client_email": "{{unique_hash}}@example.com", "client_id": "{{ timestamp("now") }}{{ timestamp("now") }}0", "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/$CLIENT_EMAIL", "host_filters": "key:value,filter:example", "cloud_run_revision_filters": ["dr:dre"], "is_cspm_enabled": true, "is_security_command_center_enabled": true, "is_resource_change_collection_enabled": true, "private_key": "private_key", "private_key_id": "123456789abcdefghi123456789abcdefghijklm", "project_id": "datadog-apitest", "resource_collection_enabled": true, "token_uri": "https://accounts.google.com/o/oauth2/token", "type": "service_account"}
@@ -31,7 +31,7 @@ Feature: GCP Integration
3131
When the request is sent
3232
Then the response status is 400 Bad Request
3333

34-
@replay-only @team:DataDog/gcp-integrations
34+
@team:DataDog/gcp-integrations
3535
Scenario: Delete a GCP integration returns "OK" response
3636
Given there is a valid "gcp_account" in the system
3737
And new "DeleteGCPIntegration" request
@@ -45,13 +45,13 @@ Feature: GCP Integration
4545
When the request is sent
4646
Then the response status is 400 Bad Request
4747

48-
@replay-only @team:DataDog/gcp-integrations
48+
@skip-terraform-config @team:DataDog/gcp-integrations
4949
Scenario: List all GCP integrations returns "OK" response
5050
Given new "ListGCPIntegration" request
5151
When the request is sent
5252
Then the response status is 200 OK
5353

54-
@replay-only @team:DataDog/gcp-integrations
54+
@team:DataDog/gcp-integrations
5555
Scenario: Update a GCP integration cloud run revision filters returns "OK" response
5656
Given there is a valid "gcp_account" in the system
5757
And new "UpdateGCPIntegration" request
@@ -66,7 +66,7 @@ Feature: GCP Integration
6666
When the request is sent
6767
Then the response status is 400 Bad Request
6868

69-
@replay-only @team:DataDog/gcp-integrations
69+
@team:DataDog/gcp-integrations
7070
Scenario: Update a GCP integration returns "OK" response
7171
Given there is a valid "gcp_account" in the system
7272
And new "UpdateGCPIntegration" request

tests/scenarios/features/v2/gcp_integration.feature

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Feature: GCP Integration
4545
When the request is sent
4646
Then the response status is 409 Conflict
4747

48-
@replay-only @team:DataDog/gcp-integrations
48+
@team:DataDog/gcp-integrations
4949
Scenario: Create a new entry for your service account returns "OK" response
5050
Given new "CreateGCPSTSAccount" request
5151
And body with value {"data": {"attributes": {"client_email": "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com", "host_filters": []}, "type": "gcp_service_account"}}
@@ -54,7 +54,7 @@ Feature: GCP Integration
5454
And the response "data.type" is equal to "gcp_service_account"
5555
And the response "data.attributes.client_email" is equal to "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com"
5656

57-
@replay-only @team:DataDog/gcp-integrations
57+
@team:DataDog/gcp-integrations
5858
Scenario: Create a new entry for your service account with account_tags returns "OK" response
5959
Given new "CreateGCPSTSAccount" request
6060
And body with value {"data": {"attributes": {"account_tags": ["lorem", "ipsum"], "client_email": "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com", "host_filters": []}, "type": "gcp_service_account"}}
@@ -64,7 +64,7 @@ Feature: GCP Integration
6464
And the response "data.attributes.client_email" is equal to "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com"
6565
And the response "data.attributes.account_tags" is equal to ["lorem", "ipsum"]
6666

67-
@replay-only @team:DataDog/gcp-integrations
67+
@team:DataDog/gcp-integrations
6868
Scenario: Create a new entry for your service account with cloud run revision filters enabled returns "OK" response
6969
Given new "CreateGCPSTSAccount" request
7070
And body with value {"data": {"attributes": {"cloud_run_revision_filters": ["meh:bleh"], "client_email": "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com", "host_filters": []}, "type": "gcp_service_account"}}
@@ -74,7 +74,7 @@ Feature: GCP Integration
7474
And the response "data.attributes.client_email" is equal to "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com"
7575
And the response "data.attributes.cloud_run_revision_filters" is equal to ["meh:bleh"]
7676

77-
@replay-only @team:DataDog/gcp-integrations
77+
@team:DataDog/gcp-integrations
7878
Scenario: Create a new entry for your service account with cspm enabled returns "OK" response
7979
Given new "CreateGCPSTSAccount" request
8080
And body with value {"data": {"attributes": {"is_cspm_enabled": true, "resource_collection_enabled": true, "client_email": "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com", "host_filters": []}, "type": "gcp_service_account"}}
@@ -84,14 +84,14 @@ Feature: GCP Integration
8484
And the response "data.attributes.client_email" is equal to "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com"
8585
And the response "data.attributes.is_cspm_enabled" is equal to true
8686

87-
@replay-only @team:DataDog/gcp-integrations
87+
@team:DataDog/gcp-integrations
8888
Scenario: Create a new entry for your service account with resource collection enabled disabled and cspm enabled returns "Bad Request" response
8989
Given new "CreateGCPSTSAccount" request
9090
And body with value {"data": {"attributes": {"resource_collection_enabled": false, "is_cspm_enabled": true, "client_email": "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com", "host_filters": []}, "type": "gcp_service_account"}}
9191
When the request is sent
9292
Then the response status is 400 Bad Request
9393

94-
@replay-only @team:DataDog/gcp-integrations
94+
@team:DataDog/gcp-integrations
9595
Scenario: Create a new entry for your service account with resource collection enabled returns "OK" response
9696
Given new "CreateGCPSTSAccount" request
9797
And body with value {"data": {"attributes": {"resource_collection_enabled": true, "client_email": "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com", "host_filters": []}, "type": "gcp_service_account"}}
@@ -101,7 +101,7 @@ Feature: GCP Integration
101101
And the response "data.attributes.client_email" is equal to "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com"
102102
And the response "data.attributes.resource_collection_enabled" is equal to true
103103

104-
@replay-only @team:DataDog/gcp-integrations
104+
@team:DataDog/gcp-integrations
105105
Scenario: Create a new entry for your service account with security command center enabled returns "OK" response
106106
Given new "CreateGCPSTSAccount" request
107107
And body with value {"data": {"attributes": {"is_security_command_center_enabled": true, "is_resource_change_collection_enabled": true, "client_email": "Test-{{ unique_hash }}@test-project.iam.gserviceaccount.com", "host_filters": []}, "type": "gcp_service_account"}}
@@ -132,15 +132,15 @@ Feature: GCP Integration
132132
When the request is sent
133133
Then the response status is 404 Not Found
134134

135-
@replay-only @team:DataDog/gcp-integrations
135+
@skip-terraform-config @team:DataDog/gcp-integrations
136136
Scenario: List all GCP STS-enabled service accounts returns "OK" response
137137
Given there is a valid "gcp_sts_account" in the system
138138
And new "ListGCPSTSAccounts" request
139139
When the request is sent
140140
Then the response status is 200 OK
141141
And the response "data" has item with field "type" with value "gcp_service_account"
142142

143-
@replay-only @team:DataDog/gcp-integrations
143+
@team:DataDog/gcp-integrations
144144
Scenario: List delegate account returns "OK" response
145145
Given new "GetGCPSTSDelegate" request
146146
When the request is sent
@@ -163,7 +163,7 @@ Feature: GCP Integration
163163
When the request is sent
164164
Then the response status is 404 Not Found
165165

166-
@replay-only @team:DataDog/gcp-integrations
166+
@team:DataDog/gcp-integrations
167167
Scenario: Update STS Service Account returns "OK" response
168168
Given there is a valid "gcp_sts_account" in the system
169169
And new "UpdateGCPSTSAccount" request
@@ -172,7 +172,7 @@ Feature: GCP Integration
172172
When the request is sent
173173
Then the response status is 201 OK
174174

175-
@replay-only @team:DataDog/gcp-integrations
175+
@team:DataDog/gcp-integrations
176176
Scenario: Update STS Service Account returns "OK" response with cloud run revision filters
177177
Given there is a valid "gcp_sts_account" in the system
178178
And new "UpdateGCPSTSAccount" request
@@ -181,7 +181,7 @@ Feature: GCP Integration
181181
When the request is sent
182182
Then the response status is 201 OK
183183

184-
@replay-only @team:DataDog/gcp-integrations
184+
@team:DataDog/gcp-integrations
185185
Scenario: Update STS Service Account returns "OK" response with enable resource collection turned on
186186
Given there is a valid "gcp_sts_account" in the system
187187
And new "UpdateGCPSTSAccount" request

0 commit comments

Comments
 (0)