Add skip-terraform-config to Dataset BDD Test (#821)

Co-authored-by: ci.datadog-api-spec <[email protected]>

Author: api-clients-generation-pipeline[bot]

.generated-info

@@ -1,4 +1,4 @@
 {
-  "spec_repo_commit": "672a533",
-  "generated": "2025-07-31 18:12:52.812"
+  "spec_repo_commit": "0f70319",
+  "generated": "2025-08-01 15:36:54.364"
 }

tests/scenarios/features/v2/datasets.feature

@@ -11,15 +11,15 @@ Feature: Datasets
     And a valid "appKeyAuth" key in the system
     And an instance of "Datasets" API
 
-  @skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-typescript @skip-validation @team:DataDog/aaa-granular-access
+  @skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-terraform-config @skip-typescript @skip-validation @team:DataDog/aaa-granular-access
   Scenario: Create a dataset returns "Bad Request" response
     Given new "CreateDataset" request
     And operation "CreateDataset" enabled
     And body with value {"test": "bad_request"}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Create a dataset returns "Conflict" response
     Given there is a valid "dataset" in the system
     And operation "CreateDataset" enabled
@@ -28,23 +28,23 @@ Feature: Datasets
     When the request is sent
     Then the response status is 409 Conflict
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Create a dataset returns "OK" response
     Given new "CreateDataset" request
     And operation "CreateDataset" enabled
     And body with value {"data": {"attributes": {"name": "Security Audit Dataset", "principals": ["role:94172442-be03-11e9-a77a-3b7612558ac1"], "product_filters": [{"filters": ["@application.id:ABCD"], "product": "metrics"}]}, "type": "dataset"}}
     When the request is sent
     Then the response status is 200 OK
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Delete a dataset returns "Bad Request" response
     Given new "DeleteDataset" request
     And operation "DeleteDataset" enabled
     And request contains "dataset_id" parameter with value "malformed_id"
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Delete a dataset returns "No Content" response
     Given there is a valid "dataset" in the system
     And operation "DeleteDataset" enabled
@@ -53,23 +53,23 @@ Feature: Datasets
     When the request is sent
     Then the response status is 204 No Content
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Delete a dataset returns "Not Found" response
     Given new "DeleteDataset" request
     And operation "DeleteDataset" enabled
     And request contains "dataset_id" parameter with value "00000000-0000-0000-0000-000000000000"
     When the request is sent
     Then the response status is 404 Not Found
 
-  @skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-typescript @skip-validation @team:DataDog/aaa-granular-access
+  @skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-terraform-config @skip-typescript @skip-validation @team:DataDog/aaa-granular-access
   Scenario: Edit a dataset returns "Bad Request" response
     Given new "UpdateDataset" request
     And operation "UpdateDataset" enabled
     And request contains "dataset_id" parameter with value "malformed_id"
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @skip @team:DataDog/aaa-granular-access
+  @skip @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Edit a dataset returns "Not Found" response
     Given there is a valid "dataset" in the system
     And operation "UpdateDataset" enabled
@@ -79,7 +79,7 @@ Feature: Datasets
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Edit a dataset returns "OK" response
     Given there is a valid "dataset" in the system
     And operation "UpdateDataset" enabled
@@ -89,23 +89,23 @@ Feature: Datasets
     When the request is sent
     Then the response status is 200 OK
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Get a single dataset by ID returns "Bad Request" response
     Given new "GetDataset" request
     And operation "GetDataset" enabled
     And request contains "dataset_id" parameter with value "malformed_id"
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @skip @team:DataDog/aaa-granular-access
+  @skip @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Get a single dataset by ID returns "Not Found" response
     Given operation "GetDataset" enabled
     And new "GetDataset" request
     And request contains "dataset_id" parameter with value "00000000-0000-0000-0000-000000000000"
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Get a single dataset by ID returns "OK" response
     Given there is a valid "dataset" in the system
     And operation "GetDataset" enabled
@@ -114,7 +114,7 @@ Feature: Datasets
     When the request is sent
     Then the response status is 200 OK
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Get all datasets returns "OK" response
     Given there is a valid "dataset" in the system
     And operation "GetAllDatasets" enabled