-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error updating aws_backup_plan #9502
Comments
I encountered this same problem, but updating the start_window of the aws_backup_plan.
|
Also encounter same problem.
|
This is still happening on terraform version 0.12.7 with the 2.25.0 provider |
This is still happening if we create a module and source out the module , it works within a resource
|
I have seen the same issue using AWS provider v2.33, terraform v0.11 I tried to come up with a simple case to reproduce the error and found that the error starts when adding Here is an example of a change that does not produce the error. Start with this resource and create it using
Now update To reproduce the error, start with the same resource as above, but now add
Now make the same update as before, e.g. update the This time you get the error:
|
Given that this looks like it's caused by changes to |
I am encountering this with: Terraform v0.12.12 |
The fixes for these issues has been merged and will release with version 2.34.0 of the Terraform AWS Provider, on Thursday. Thanks to @ewbankkit for the implementation. |
This has been released in version 2.34.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
This issue was originally opened by @totallyben as hashicorp/terraform#22205. It was migrated here as a result of the provider split. The original body of the issue is below.
Trying to modify the schedule on an existing aws_backup_plan results in the following error:
Only the schedule has changed and the rule name and target backup vault do exist. The output plan from the apply looks like:
The text was updated successfully, but these errors were encountered: