You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plan shows that the replication_specs object is recreated with disk_gb_enabled = false
Run terraform apply
Expected Behavior
After the apply, storage auto scaling is disabled and subsequent plans don't show any changes
Actual Behavior
Storage auto scaling is enabled when looking at the UI (Cluster Configuration). Subsequent plan/apply runs still want to recreate replication_specs because of storage_autoscaling_enabled -> false but it stays enabled.
Debug Output
Not yet possible for me to create, since the migration to advanced cluster is currently on hold in our project. Nevertheless, I hope that this case is easy enough to reproduce very fast; otherwise I can try to do this the next days.
The text was updated successfully, but these errors were encountered:
@BlacCello As per the repro, this seems to be underlying API issue and not related to Terraform provider. I have filed an internal ticket to address this. It is better we can close this here as this will be handled for the API releases and not with Terraform provider.
Terraform CLI and Terraform MongoDB Atlas Provider Version
Steps to Reproduce
Create a cluster with the following settings
The plan shows that the replication_specs object is recreated with
disk_gb_enabled = false
Run
terraform apply
Expected Behavior
After the apply, storage auto scaling is disabled and subsequent plans don't show any changes
Actual Behavior
Storage auto scaling is enabled when looking at the UI (Cluster Configuration). Subsequent plan/apply runs still want to recreate replication_specs because of
storage_autoscaling_enabled -> false
but it stays enabled.Debug Output
Not yet possible for me to create, since the migration to advanced cluster is currently on hold in our project. Nevertheless, I hope that this case is easy enough to reproduce very fast; otherwise I can try to do this the next days.
The text was updated successfully, but these errors were encountered: