Quirk in how AWS DMS handles case sensitivity presents as "bug" in terraform. Resources constantly destroyed and recreated.

[sforcier]

This is perhaps a feature request more than a bug because this appears to be a quirk in AWS. In short, AWS allows you to create most DMS resources (confirmed with tasks, endpoints, replication instances, and subnet groups) with case insensitive names, but when the resource is created, it's converted to all lowercase. This causes terraform to always identify a change because "sometaskname" => "SomeTaskName" is seen as a legit change.

No clue if this request is reasonable, but if one of the following happened that'd be great:

• A warning is presented in either the documentation or as an output of my apply.
• Terraform did a case insensitive comparison for affected items in the aws_dms_* resources.

Terraform Version

0.10.7

Affected Resource(s)

aws_dms_

References

Similar in outward behavior, but due to a different root cause than 1513.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[ghost]

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!