Hi,

I’m facing an issue about Snapshot Backup Policy creation/modification via Terraform ( FYI, I open a case to the support of MongoDB  https://support.mongodb.com/case/00668262). Let me explain :

When I want to create a MongoAtlas Cluster via terraform, I want to apply a custom Snahsphot Backup Policy with ONLY 2 items during the creation of the cluster :
N° Item Frequency type Frequency Retention
0 Daily 1 7 Days
1 Weekly 1 (Saturday) 4 weeks

However, during the creation of the mongo atlas cluster, I can see an error
Error: Error applying plan:

1 error occurred:
* module.clustercontrib.module.dpjmongoatlas.module.tfmodule-gcp-mongo-atlas-cluster.mongodbatlascloudprovidersnapshotbackuppolicy.snapshotbackup: 1 error occurred:
* mongodbatlascloudprovidersnapshotbackuppolicy.snapshot_backup: error updating a Cloud Provider Snapshot Backup Policy: PATCH https://cloud.mongodb.com/api/atlas/v1.0/groups/XXXXXXXXXXXXXXXXX/clusters/contrib/backup/schedule: 400 (request "Bad Request") The frequency type of a policy item must not be changed.

Indeed, during the creation of the MongoAtlas cluster, MongoAtlas apply the default Snapshot Backup Policy first (with 4 items hourly, daily, weekly, monthly) and after try to apply the custom snapshot backup policy I want (described in the terraform code). But, as we can see above, it seems impossible to change the frequency_type of an existing policy’s item…

To resume clearly with this spreadsheet :
N° Item Frequencytype of default policy Frequencytype of custom policy I want COMMENT
0 Hourly Daily KO (because The frequency type of a policy item must not be changed)

1 Daily Weekly KO (because The frequency type of a policy item must not be changed)

2 Weekly NOTHING
3 Monthly NOTHING

Can we purpose a evolution to have the possibilty to modify the frequency_type of an existing policy item via Terraform/API?

Regards,

Current resource

resource "mongodbatlas_cluster" "cluster" {
  project_id   = var.project_id
  name         = var.cluster_name
  disk_size_gb = var.disk_size_gb
  num_shards   = var.num_shards
  replication_factor           = var.replication_factor
  auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled
  mongo_db_major_version       = var.mongo_db_major_version
  //Provider Settings "block"
  provider_name               = var.provider_name
  provider_disk_iops          = var.provider_disk_iops
  provider_volume_type        = var.provider_volume_type
  provider_instance_size_name = var.provider_instance_size_name
  provider_region_name        = var.provider_region_name
  provider_backup_enabled      = var.provider_backup_enabled
}

Suggested resource

resource "mongodbatlas_cluster" "cluster" {
  project_id   = var.project_id
  name         = var.cluster_name
  disk_size_gb = var.disk_size_gb
  num_shards   = var.num_shards
  replication_factor           = var.replication_factor
  auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled
  mongo_db_major_version       = var.mongo_db_major_version
  //Provider Settings "block"
  cluster_provider = {
    name               = var.provider_name
    disk_iops          = var.provider_disk_iops
    volume_type        = var.provider_volume_type
    instance_size_name = var.provider_instance_size_name
    region_name        = var.provider_region_name
    backup_enabled     = var.provider_backup_enabled
  }
}

cluster_provider property will be a map of configuration for provider.

Hello,
We initially rolled out all our clusters with mongo atlas terraform provider version 0.7.0. Since we hadn't pinned the version, we started seeing warning listed below in the terraform plan.

Updating as indicated based on the warning means, a deletion and recreation of the private endpoint/link related resources which will lead to downtime as the cluster will be inaccessible while the private endpoint/link is being recreated.

Ideally migration of terraform state should be handled or provide a tool for migrating state so the resource can be migrated without recreation.

============================================

There are warnings related to your configuration. If no errors occurred,
Terraform will continue despite these warnings. It is a good idea to resolve
these warnings in the near future.

Warnings:
module.mongodbatlasds.mongodbatlasprivateendpoint.atlasprivateendpoint: this resource is deprecated, please transition as soon as possible to mongodbatlasprivatelinkendpoint
module.mongodbatlasds.mongodbatlasprivateendpointinterfacelink.atlasprivateendpointinterfacelink: this resource is deprecated, please transition as soon as possible to mongodbatlasprivatelinkendpoint_service

We did try using the import example but unfortunately ran into this issue:

Error importing: Provider "mongodbatlas" depends on non-var "data.external.mongoatlasvaultcredentials.0/data.external.mongoatlasvaultcredentials.N". Providers for import can currently only depend on variables or must be hardcoded. You can stop import from loading configurations by specifying -config="".

https://github.com/hashicorp/terraform/issues/17847

Our provider configuration is something like this where it pulls the credentials from vault using a script:
provider"mongodbatlas"{
version="0.8.2"
publickey="${data.external.mongoatlasvaultcredentials.result.publickey}"
privatekey="${data.external.mongoatlasvaultcredentials.result.privatekey}"
}

Now just for the sake of trying, I did hard code the pubic key/private key in the provider for my dev dc and in that case, the import does work as expected. But since we have 10 data centers for which we have different keys, it's not possible for us to hard code anything since the same code is used for all the DCs. So even though the import option can work for a simple deployment test, it's not a working solution for us.