Closed Frank-Reichenbach closed 3 months ago
Thanks for opening this issue! Please make sure you've followed our guidelines when opening the issue. In short, to help us reproduce the issue we need:
The ticket CLOUDP-259859 was created for internal tracking.
Wow, thats not even 24h after I created the issue. Thank you for the prompt resolution of the issue, can't wait to see the new release!
@Frank-Reichenbach thank you for opening this issue and the clear reproduction details! The fix should be part of the next release 👍
Wir haben auf das neue Release v1.17.4 aktualisiert und getestet, funktioniert wie erwartet 👍
Is there an existing issue for this?
Provider Version
v1.15.3 and v1.17.3
Terraform Version
v1.9.0
Terraform Edition
Terraform Open Source (OSS)
Current Behavior
When I change my resource configuration for the mongodbatlas_cloud_backup_schedule resource, I expected, that when I omit the copy_settings section, it would turn off the ADDITIONAL BACKUP COPIES for my backup policies, but it didn't.
I have 2 different backup policies, one "advanced" which provides the copy_settings section to create additional copies of the backup snapshots, and another one which doesn`t. After creating a mongodbatlas_cloud_backup_schedule with the copy_settings provided, it turns on the ADDITIONAL BACKUP COPIES correctly. But switching back to my basic backup policies, without the copy_settings, it did not turn off the ADDITIONAL BACKUP COPIES, as I expected.
Terraform configuration to reproduce the issue
Steps To Reproduce
tf apply
finished without errorsLogs
Code of Conduct