-
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
Perpetual diff with aws_dms_replication_task #19883
Comments
hitting this as well |
This is probably somewhat related to #1513. I guess that #13476 was good at the time, but since then AWS have added more read-only settings. The workaround at #1513 (comment) is okay-ish (drop the quotes to avoid the deprecation warnings). |
Hitting a similar issue with version v4.3.0. It seems that #23328 didn't fix it In my case, the change in the plan shows changes on
|
Facing the same issue:
Terraform: 1.2.9 |
Also running into this with the most recent AWS provider as of today. We've had this running for months without anything coming up and then today it just decided this was needed.
Terraform: 1.3.4 |
This functionality has been released in v4.65.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm running into this on the latest v4.66.1. The diff shows the LogComponents as needing a change due to re-ordering of the array which matches the original issue. The PR's that were meant to fix this look like they target other fields for some reason? |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
The
dms-task-settings.json
is also pertinent; it's simply all of DMS' defaults, written with the intent of producing a zero-diff:Debug Output
N/A
Panic Output
N/A
Expected Behavior
Running
terraform plan
immediately after applying the above resource should show no diffs.Actual Behavior
terraform plan
shows diffs in thereplication_task_settings.Logging.LogComponents
:Steps to Reproduce
terraform apply
terraform plan
Important Factoids
References
The text was updated successfully, but these errors were encountered: