Closed icco closed 1 month 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-261296 was created for internal tracking.
Hi @icco, thank you for raising the ticket.
The main issue with the configuration shared above is that there are multiple mongodbatlas_maintenance_window
resources defined for the same project, which is not the intended use case. Only a single maintenance window configuration is expected to be defined per project. From the Maintenance Window documentation you will see that automated maintenance runs on a weekly basis, giving users the flexibility to define at which day and hour it is run.
Opened a PR so we clarify this in our mongodbatlas_maintenance_window
resource documentation: https://github.com/mongodb/terraform-provider-mongodbatlas/pull/2418.
Fascinating. Thank you. I kind of wish the backend would throw an error, given it looks like each window has a unique ID.
Is there an existing issue for this?
Provider Version
v1.17.3
Terraform Version
v1.5.3
Terraform Edition
Terraform Open Source (OSS)
Current Behavior
Every plan and apply we run the maintence windows change, even though the code hasn't changed at all.
Terraform configuration to reproduce the issue
Steps To Reproduce
resource.mongodbatlas_project.project
)Logs
No response
Code of Conduct