deprecate: marking cloud_provider_access resource and data source as …

…deprecated
mongodb · Jul 28, 2023 · e110bac · e110bac
1 parent 23f9757
commit e110bac
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 1 deletion.
diff --git a/mongodbatlas/data_source_mongodbatlas_cloud_provider_access.go b/mongodbatlas/data_source_mongodbatlas_cloud_provider_access.go
@@ -16,7 +16,8 @@ const (
 
 func dataSourceMongoDBAtlasCloudProviderAccessList() *schema.Resource {
 	return &schema.Resource{
-		ReadContext: dataSourceMongoDBAtlasCloudProviderAccessRead,
+		ReadContext:        dataSourceMongoDBAtlasCloudProviderAccessRead,
+		DeprecationMessage: fmt.Sprintf(DeprecationMessage, "v1.14.0", "mongodbatlas_cloud_provider_access"),
 		Schema: map[string]*schema.Schema{
 			"project_id": {
 				Type:     schema.TypeString,

diff --git a/mongodbatlas/resource_mongodbatlas_cloud_provider_access.go b/mongodbatlas/resource_mongodbatlas_cloud_provider_access.go
@@ -28,6 +28,7 @@ func resourceMongoDBAtlasCloudProviderAccess() *schema.Resource {
 		Importer: &schema.ResourceImporter{
 			StateContext: resourceMongoDBAtlasCloudProviderAccessImportState,
 		},
+		DeprecationMessage: fmt.Sprintf(DeprecationMessage, "v1.14.0", "mongodbatlas_cloud_provider_access"),
 		Schema: map[string]*schema.Schema{
 			"project_id": {
 				Type:     schema.TypeString,

diff --git a/website/docs/d/cloud_provider_access.markdown b/website/docs/d/cloud_provider_access.markdown
@@ -6,6 +6,8 @@ description: |-
     Allows you to get the list of cloud provider access roles
 ---
 
+**WARNING:** The data source `mongodbatlas_cloud_provider_access` is deprecated and will be removed in version v1.14.0, use the data source `mongodbatlas_cloud_provider_access_setup` instead.
+
 # Data Source: mongodbatlas_cloud_provider_access
 
 `mongodbatlas_cloud_provider_access` allows you to get the list of cloud provider access roles, currently only AWS is supported.

diff --git a/website/docs/r/cloud_provider_access.markdown b/website/docs/r/cloud_provider_access.markdown
@@ -11,6 +11,7 @@ description: |-
 The Terraform MongoDB Atlas Provider offers two either-or/mutually exclusive paths to perform an authorization for a cloud provider role -
 
 * A Single Resource path: using the `mongodbatlas_cloud_provider_access` that at provision time sets up all the required configuration for a given provider, then with a subsequent update it can perform the authorize of the role. Note this path requires two `terraform apply` commands, once for setup and once for auth.
+**WARNING:** The resource `mongodbatlas_cloud_provider_access` is deprecated and will be removed in version v1.14.0, use the Two Resource path instead.
 
 * A Two Resource path: consisting of `mongodbatlas_cloud_provider_access_setup` and `mongodbatlas_cloud_provider_access_authorization`. The first resource, `mongodbatlas_cloud_provider_access_setup`, only generates
 the initial configuration (create, delete operations). The second resource, `mongodbatlas_cloud_provider_access_authorization`, helps to perform the authorization using the role_id of the first resource. This path is helpful in a multi-provider Terraform file, and allows for a single and decoupled apply. See example of this Two Resource path option with AWS Cloud [here](https://github.com/mongodb/terraform-provider-mongodbatlas/tree/master/examples/atlas-cloud-provider-access/aws). 
@@ -19,6 +20,8 @@ the initial configuration (create, delete operations). The second resource, `mon
 
 ## mongodbatlas_cloud_provider_access
 
+**WARNING:** The resource `mongodbatlas_cloud_provider_access` is deprecated and will be removed in version v1.14.0, use the Two Resource path instead.
+
 `mongodbatlas_cloud_provider_access` Allows you to register and authorize AWS IAM roles in Atlas. This is the resource to use for the single resource path described above.
 
 -> **NOTE:** Groups and projects are synonymous terms. You may find `groupId` in the official documentation.