-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[Bug]: aws_dms_replication_config has persistent changes #35573
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v5.42.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 going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.3.1
AWS Provider Version
5.34.0
Affected Resource(s)
aws_dms_replication_config
Expected Behavior
Apply config parameters consistently
Actual Behavior
It wants to remove the replication_settings and it is not configured by terraform. In my replication_settings, I just configure the "Logging" settings. However, the terraform plan show many changes of replication_settings.
I have reported issue #35493 and it said this bug is fixed in 5.32.0. However, this issue still exists in 5.34.0.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
apply the configuration to create a dms serverless application
try to apply again and receive the error above
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: