Promote unstable aws v2 APIs and deprecate v1 (#2766)

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

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

.generator/schemas/v1/openapi.yaml

@@ -27347,6 +27347,7 @@ paths:
         - hosts_read
   /api/v1/integration/aws:
     delete:
+      deprecated: true
       description: Delete a Datadog-AWS integration matching the specified `account_id`
         and `role_name parameters`.
       operationId: DeleteAWSAccount
@@ -27393,6 +27394,7 @@ paths:
         permissions:
         - aws_configurations_manage
     get:
+      deprecated: true
       description: List all Datadog-AWS integrations available in your Datadog organization.
       operationId: ListAWSAccounts
       parameters:
@@ -27443,6 +27445,7 @@ paths:
         permissions:
         - aws_configuration_read
     post:
+      deprecated: true
       description: 'Create a Datadog-Amazon Web Services integration.
 
         Using the `POST` method updates your integration configuration
@@ -27494,6 +27497,7 @@ paths:
         permissions:
         - aws_configurations_manage
     put:
+      deprecated: true
       description: Update a Datadog-Amazon Web Services integration.
       operationId: UpdateAWSAccount
       parameters:
@@ -27563,6 +27567,7 @@ paths:
         - aws_configuration_edit
   /api/v1/integration/aws/available_namespace_rules:
     get:
+      deprecated: true
       description: List all namespace rules for a given Datadog-AWS integration. This
         endpoint takes no arguments.
       operationId: ListAvailableAWSNamespaces
@@ -27708,6 +27713,7 @@ paths:
         - manage_integrations
   /api/v1/integration/aws/filtering:
     delete:
+      deprecated: true
       description: Delete a tag filtering entry.
       operationId: DeleteAWSTagFilter
       requestBody:
@@ -27749,6 +27755,7 @@ paths:
         permissions:
         - aws_configuration_edit
     get:
+      deprecated: true
       description: Get all AWS tag filters.
       operationId: ListAWSTagFilters
       parameters:
@@ -27787,6 +27794,7 @@ paths:
         permissions:
         - aws_configuration_read
     post:
+      deprecated: true
       description: Set an AWS tag filter.
       operationId: CreateAWSTagFilter
       requestBody:
@@ -27832,6 +27840,7 @@ paths:
         - aws_configuration_edit
   /api/v1/integration/aws/generate_new_external_id:
     put:
+      deprecated: true
       description: Generate a new AWS external ID for a given AWS account ID and role
         name pair.
       operationId: CreateNewAWSExternalID
@@ -27917,6 +27926,7 @@ paths:
         permissions:
         - aws_configuration_edit
     get:
+      deprecated: true
       description: List all Datadog-AWS Logs integrations configured in your Datadog
         account.
       operationId: ListAWSLogsIntegrations
@@ -28058,6 +28068,7 @@ paths:
         - aws_configuration_read
   /api/v1/integration/aws/logs/services:
     get:
+      deprecated: true
       description: Get the list of current AWS services that Datadog offers automatic
         log collection. Use returned service IDs with the services parameter for the
         Enable an AWS service log collection API endpoint.
@@ -28100,6 +28111,7 @@ paths:
         permissions:
         - aws_configuration_read
     post:
+      deprecated: true
       description: Enable automatic log collection for a list of services. This should
         be run after running `CreateAWSLambdaARN` to save the configuration.
       operationId: EnableAWSLogServices

.generator/schemas/v2/openapi.yaml

@@ -55263,9 +55263,6 @@ paths:
         operator: OR
         permissions:
         - aws_configuration_read
-      x-unstable: '**Note: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).**'
     post:
       description: Create a new AWS Account Integration Config.
       operationId: CreateAWSAccount
@@ -55298,9 +55295,6 @@ paths:
         operator: OR
         permissions:
         - aws_configurations_manage
-      x-unstable: '**Note: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).**'
   /api/v2/integration/aws/accounts/{aws_account_config_id}:
     delete:
       description: Delete an AWS Account Integration Config by config ID.
@@ -55325,9 +55319,6 @@ paths:
         operator: OR
         permissions:
         - aws_configurations_manage
-      x-unstable: '**Note: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).**'
     get:
       description: Get an AWS Account Integration Config by config ID.
       operationId: GetAWSAccount
@@ -55355,9 +55346,6 @@ paths:
         operator: OR
         permissions:
         - aws_configuration_read
-      x-unstable: '**Note: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).**'
     patch:
       description: Update an AWS Account Integration Config by config ID.
       operationId: UpdateAWSAccount
@@ -55392,9 +55380,6 @@ paths:
         operator: OR
         permissions:
         - aws_configuration_edit
-      x-unstable: '**Note: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).**'
   /api/v2/integration/aws/available_namespaces:
     get:
       description: Get a list of available AWS CloudWatch namespaces that can send
@@ -55418,9 +55403,6 @@ paths:
         operator: OR
         permissions:
         - aws_configuration_read
-      x-unstable: '**Note: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).**'
   /api/v2/integration/aws/generate_new_external_id:
     post:
       description: Generate a new external ID for AWS role-based authentication.
@@ -55443,9 +55425,6 @@ paths:
         operator: OR
         permissions:
         - aws_configuration_edit
-      x-unstable: '**Note: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).**'
   /api/v2/integration/aws/iam_permissions:
     get:
       description: Get all AWS IAM permissions required for the AWS integration.
@@ -55484,9 +55463,6 @@ paths:
         operator: OR
         permissions:
         - aws_configuration_read
-      x-unstable: '**Note: This endpoint is in public beta. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).**'
   /api/v2/integration/gcp/accounts:
     get:
       description: List all GCP STS-enabled service accounts configured in your Datadog

features/v2/aws_integration.feature

@@ -11,74 +11,65 @@ Feature: AWS Integration
 
   @team:DataDog/aws-integrations
   Scenario: Create an AWS account returns "AWS Account object" response
-    Given operation "CreateAWSAccount" enabled
-    And new "CreateAWSAccount" request
+    Given new "CreateAWSAccount" request
     And body with value {"data": {"attributes": {"account_tags": ["key:value"], "auth_config": {"role_name": "DatadogIntegrationRole"}, "aws_account_id": "123456789012", "aws_partition": "aws", "logs_config": {"lambda_forwarder": {"lambdas": ["arn:aws:lambda:us-east-1:123456789012:function:DatadogLambdaLogForwarder"], "log_source_config": {"tag_filters": [{"source": "s3", "tags": ["test:test"]}]}, "sources": ["s3"]}}, "metrics_config": {"automute_enabled": true, "collect_cloudwatch_alarms": true, "collect_custom_metrics": true, "enabled": true, "tag_filters": [{"namespace": "AWS/EC2", "tags": ["key:value"]}]}, "resources_config": {"cloud_security_posture_management_collection": false, "extended_collection": false}, "traces_config": {}}, "type": "account"}}
     When the request is sent
     Then the response status is 200 AWS Account object
 
   @team:DataDog/aws-integrations
   Scenario: Create an AWS integration returns "AWS Account object" response
-    Given operation "CreateAWSAccount" enabled
-    And new "CreateAWSAccount" request
+    Given new "CreateAWSAccount" request
     And body with value {"data": {"attributes": {"account_tags": ["key:value"], "auth_config": {"access_key_id": "AKIAIOSFODNN7EXAMPLE", "secret_access_key": "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"}, "aws_account_id": "123456789012", "aws_partition": "aws", "logs_config": {"lambda_forwarder": {"lambdas": ["arn:aws:lambda:us-east-1:123456789012:function:DatadogLambdaLogForwarder"], "log_source_config": {"tag_filters": [{"source": "s3", "tags": ["test:test"]}]}, "sources": ["s3"]}}, "metrics_config": {"automute_enabled": true, "collect_cloudwatch_alarms": true, "collect_custom_metrics": true, "enabled": true, "tag_filters": [{"namespace": "AWS/EC2", "tags": ["key:value"]}]}, "resources_config": {"cloud_security_posture_management_collection": false, "extended_collection": false}, "traces_config": {}}, "type": "account"}}
     When the request is sent
     Then the response status is 200 AWS Account object
 
   @team:DataDog/aws-integrations
   Scenario: Create an AWS integration returns "Bad Request" response
-    Given operation "CreateAWSAccount" enabled
-    And new "CreateAWSAccount" request
+    Given new "CreateAWSAccount" request
     And body with value {"data": {"attributes": {"account_tags": ["key:value"], "auth_config": {"role_name": "DatadogIntegrationRole"}, "aws_account_id": "123456789012", "aws_partition": "aws-invalid", "logs_config": {"lambda_forwarder": {"lambdas": ["arn:aws:lambda:us-east-1:123456789012:function:DatadogLambdaLogForwarder"], "log_source_config": {"tag_filters": [{"source": "s3", "tags": ["test:test"]}]}, "sources": ["s3"]}}, "metrics_config": {"automute_enabled": true, "collect_cloudwatch_alarms": true, "collect_custom_metrics": true, "enabled": true, "tag_filters": [{"namespace": "AWS/EC2", "tags": ["key:value"]}]}, "resources_config": {"cloud_security_posture_management_collection": false, "extended_collection": false}, "traces_config": {}}, "type": "account"}}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @team:DataDog/aws-integrations
   Scenario: Create an AWS integration returns "Conflict" response
-    Given operation "CreateAWSAccount" enabled
-    And there is a valid "aws_account_v2" in the system
+    Given there is a valid "aws_account_v2" in the system
     And new "CreateAWSAccount" request
     And body with value {"data": {"attributes": {"account_tags": ["key:value"], "auth_config": {"role_name": "DatadogIntegrationRole"}, "aws_account_id": "123456789012", "aws_partition": "aws", "logs_config": {"lambda_forwarder": {"lambdas": ["arn:aws:lambda:us-east-1:123456789012:function:DatadogLambdaLogForwarder"], "log_source_config": {"tag_filters": [{"source": "s3", "tags": ["test:test"]}]}, "sources": ["s3"]}}, "metrics_config": {"automute_enabled": true, "collect_cloudwatch_alarms": true, "collect_custom_metrics": true, "enabled": true, "tag_filters": [{"namespace": "AWS/EC2", "tags": ["key:value"]}]}, "resources_config": {"cloud_security_posture_management_collection": false, "extended_collection": false}, "traces_config": {}}, "type": "account"}}
     When the request is sent
     Then the response status is 409 Conflict
 
   @team:DataDog/aws-integrations
   Scenario: Delete an AWS integration returns "Bad Request" response
-    Given operation "DeleteAWSAccount" enabled
-    And new "DeleteAWSAccount" request
+    Given new "DeleteAWSAccount" request
     And request contains "aws_account_config_id" parameter with value "not-a-uuid"
     When the request is sent
     Then the response status is 400 Bad Request
 
   @team:DataDog/aws-integrations
   Scenario: Delete an AWS integration returns "No Content" response
-    Given operation "DeleteAWSAccount" enabled
-    And there is a valid "aws_account_v2" in the system
+    Given there is a valid "aws_account_v2" in the system
     And new "DeleteAWSAccount" request
     And request contains "aws_account_config_id" parameter from "aws_account_v2.data.id"
     When the request is sent
     Then the response status is 204 No Content
 
   @team:DataDog/aws-integrations
   Scenario: Delete an AWS integration returns "Not Found" response
-    Given operation "DeleteAWSAccount" enabled
-    And there is a valid "aws_account_v2" in the system
+    Given there is a valid "aws_account_v2" in the system
     And new "DeleteAWSAccount" request
     And request contains "aws_account_config_id" parameter with value "448169a8-251c-4344-abee-1c4edef39f7a"
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/aws-integrations
   Scenario: Generate a new external ID returns "AWS External ID object" response
-    Given operation "CreateNewAWSExternalID" enabled
-    And new "CreateNewAWSExternalID" request
+    Given new "CreateNewAWSExternalID" request
     When the request is sent
     Then the response status is 200 AWS External ID object
 
   @team:DataDog/aws-integrations
   Scenario: Generate new external ID returns "AWS External ID object" response
-    Given operation "CreateNewAWSExternalID" enabled
-    And new "CreateNewAWSExternalID" request
+    Given new "CreateNewAWSExternalID" request
     When the request is sent
     Then the response status is 200 AWS External ID object
 
@@ -90,54 +81,47 @@ Feature: AWS Integration
 
   @team:DataDog/aws-integrations
   Scenario: Get an AWS integration by config ID returns "AWS Account object" response
-    Given operation "GetAWSAccount" enabled
-    And there is a valid "aws_account_v2" in the system
+    Given there is a valid "aws_account_v2" in the system
     And new "GetAWSAccount" request
     And request contains "aws_account_config_id" parameter from "aws_account_v2.data.id"
     When the request is sent
     Then the response status is 200 AWS Account object
 
   @team:DataDog/aws-integrations
   Scenario: Get an AWS integration by config ID returns "Bad Request" response
-    Given operation "GetAWSAccount" enabled
-    And new "GetAWSAccount" request
+    Given new "GetAWSAccount" request
     And request contains "aws_account_config_id" parameter with value "not-a-uuid"
     When the request is sent
     Then the response status is 400 Bad Request
 
   @team:DataDog/aws-integrations
   Scenario: Get an AWS integration by config ID returns "Not Found" response
-    Given operation "GetAWSAccount" enabled
-    And new "GetAWSAccount" request
+    Given new "GetAWSAccount" request
     And request contains "aws_account_config_id" parameter with value "448169a8-251c-4344-abee-1c4edef39f7a"
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/aws-integrations
   Scenario: List all AWS integrations returns "AWS Accounts List object" response
-    Given operation "ListAWSAccounts" enabled
-    And new "ListAWSAccounts" request
+    Given new "ListAWSAccounts" request
     When the request is sent
     Then the response status is 200 AWS Accounts List object
 
   @team:DataDog/aws-integrations
   Scenario: List available namespaces returns "AWS Namespaces List object" response
-    Given operation "ListAWSNamespaces" enabled
-    And new "ListAWSNamespaces" request
+    Given new "ListAWSNamespaces" request
     When the request is sent
     Then the response status is 200 AWS Namespaces List object
 
   @team:DataDog/aws-integrations
   Scenario: List namespaces returns "AWS Namespaces List object" response
-    Given operation "ListAWSNamespaces" enabled
-    And new "ListAWSNamespaces" request
+    Given new "ListAWSNamespaces" request
     When the request is sent
     Then the response status is 200 AWS Namespaces List object
 
   @team:DataDog/aws-integrations
   Scenario: Update an AWS integration returns "AWS Account object" response
-    Given operation "UpdateAWSAccount" enabled
-    And there is a valid "aws_account_v2" in the system
+    Given there is a valid "aws_account_v2" in the system
     And new "UpdateAWSAccount" request
     And request contains "aws_account_config_id" parameter from "aws_account_v2.data.id"
     And body with value {"data": {"attributes": {"account_tags": ["key:value"], "auth_config": {"role_name": "DatadogIntegrationRole"}, "aws_account_id": "123456789012", "aws_partition": "aws", "logs_config": {"lambda_forwarder": {"lambdas": ["arn:aws:lambda:us-east-1:123456789012:function:DatadogLambdaLogForwarder"], "log_source_config": {"tag_filters": [{"source": "s3", "tags": ["test:test"]}]}, "sources": ["s3"]}}, "metrics_config": {"automute_enabled": true, "collect_cloudwatch_alarms": true, "collect_custom_metrics": true, "enabled": true, "tag_filters": [{"namespace": "AWS/EC2", "tags": ["key:value"]}]}, "resources_config": {"cloud_security_posture_management_collection": false, "extended_collection": false}, "traces_config": {}}, "type": "account"}}
@@ -146,8 +130,7 @@ Feature: AWS Integration
 
   @team:DataDog/aws-integrations
   Scenario: Update an AWS integration returns "Bad Request" response
-    Given operation "UpdateAWSAccount" enabled
-    And there is a valid "aws_account_v2" in the system
+    Given there is a valid "aws_account_v2" in the system
     And new "UpdateAWSAccount" request
     And request contains "aws_account_config_id" parameter from "aws_account_v2.data.id"
     And body with value {"data": {"attributes": {"account_tags": ["key:value"], "auth_config": {"access_key_id": "AKIAIOSFODNN7EXAMPLE", "secret_access_key": "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"}, "aws_account_id": "123456789012", "aws_partition": "aws", "logs_config": {"lambda_forwarder": {"lambdas": ["arn:aws:lambda:us-east-1:123456789012:function:DatadogLambdaLogForwarder"], "log_source_config": {"tag_filters": [{"source": "s3", "tags": ["test:test"]}]}, "sources": ["s3"]}}, "metrics_config": {"automute_enabled": true, "collect_cloudwatch_alarms": true, "collect_custom_metrics": true, "enabled": true, "tag_filters": [{"namespace": "AWS/EC2", "tags": ["key:value"]}]}, "resources_config": {"cloud_security_posture_management_collection": false, "extended_collection": false}, "traces_config": {}}, "type": "account"}}
@@ -156,8 +139,7 @@ Feature: AWS Integration
 
   @team:DataDog/aws-integrations
   Scenario: Update an AWS integration returns "Not Found" response
-    Given operation "UpdateAWSAccount" enabled
-    And new "UpdateAWSAccount" request
+    Given new "UpdateAWSAccount" request
     And request contains "aws_account_config_id" parameter with value "448169a8-251c-4344-abee-1c4edef39f7a"
     And body with value {"data": {"attributes": {"account_tags": ["key:value"], "auth_config": {"role_name": "DatadogIntegrationRole"}, "aws_account_id": "123456789012", "aws_partition": "aws", "logs_config": {"lambda_forwarder": {"lambdas": ["arn:aws:lambda:us-east-1:123456789012:function:DatadogLambdaLogForwarder"], "log_source_config": {"tag_filters": [{"source": "s3", "tags": ["test:test"]}]}, "sources": ["s3"]}}, "metrics_config": {"automute_enabled": true, "collect_cloudwatch_alarms": true, "collect_custom_metrics": true, "enabled": true, "tag_filters": [{"namespace": "AWS/EC2", "tags": ["key:value"]}]}, "resources_config": {"cloud_security_posture_management_collection": false, "extended_collection": false}, "traces_config": {}}, "type": "account"}}
     When the request is sent

features/v2/aws_logs_integration.feature

@@ -10,7 +10,6 @@ Feature: AWS Logs Integration
     Given a valid "apiKeyAuth" key in the system
     And a valid "appKeyAuth" key in the system
     And an instance of "AWSLogsIntegration" API
-    And operation "ListAWSLogsServices" enabled
     And new "ListAWSLogsServices" request
     When the request is sent
     Then the response status is 200 AWS Logs Services List object

services/aws_integration/README.md

@@ -26,14 +26,6 @@ import { AWSIntegrationApiV2 } from "@datadog/datadog-api-client-aws-integration
 import { v2 } from "@datadog/datadog-api-client-aws-integration";
 
 const configuration = createConfiguration();
-// Enable unstable operations
-const configurationOpts = {
-    unstableOperations: {
-        "AWSIntegrationApi.v2.listAWSAccounts": true
-    }
-}
-
-const configuration = createConfiguration(configurationOpts);
 const apiInstance = new AWSIntegrationApiV2(configuration);
 const params = {/* parameters */};