[Enhancement]: Deprecate uppercase versions of engine attribute in elasticache resource types

[gdavison]

Description

A number of resource types in elasticache support both uppercase and lowercase versions of the engine attribute. Update them to standardize on the default lowercase. This will eventually allow removing diff suppression from the attribute.

Add deprecation warnings for uppercase values.

Affected Resource(s) and/or Data Source(s)

• aws_elasticache_replication_group
• aws_elasticache_serverless_cache
• aws_elasticache_user
• aws_elasticache_user_group

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[jar-b]

Breaking down the current state of case sensitivity and suppression functions in impacted resources. In order to be in-scope, the arguments validation must allow case insensitive values and include a diff suppression function.

Resource	Case Insensitive	Diff Suppression	In-Scope
aws_elasticache_cluster 1	No	No	No
aws_elasticache_replication_group 2	Yes	No	No
aws_elasticache_serverless_cache 3	N/A (no validation at all)	No	No
aws_elasticache_user 4	Yes	Yes	Yes
aws_elasticache_user_group 5	Yes	Yes	Yes

[jar-b]

Closed via #42419. These changes will be available in the v6.0.0 beta release later this month.

[github-actions]

Warning

This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.