Skip to content

fix: Case insensitive matching deprecated #48

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mengesb
Copy link

@mengesb mengesb commented Jul 29, 2025

Description

Motivation and Context

Case insensitive matching has been deprecated on elasticache_user resource

Breaking Changes

This should not be a breaking change

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@mengesb
Copy link
Author

mengesb commented Jul 29, 2025

The default use of the user-group module results in an engine value of REDIS, this should now be redis per the following error message:

Warning: Case Insensitive Matching Deprecated
with module.elasticache_user_group.aws_elasticache_user.default[0]
on .terraform/modules/elasticache_user_group/modules/user-group/main.tf line 36, in resource "aws_elasticache_user" "default":
  engine               = try(var.default_user.engine, "REDIS")
Expected an exact match to "redis", got "REDIS". Case insensitive matching is deprecated for this argument. Update the value to an exact match to suppress this warning and avoid breaking changes in a future major version.

@mengesb mengesb changed the title Case insensitive matching deprecated FIX: Case insensitive matching deprecated Jul 29, 2025
@mengesb mengesb changed the title FIX: Case insensitive matching deprecated fix: Case insensitive matching deprecated Jul 29, 2025
@mengesb
Copy link
Author

mengesb commented Jul 29, 2025

As a work around, if in the default_user {} or user {} blocks, the user can specify the engine parameter and assign redis to bypass it, however the default module behavior produces this behavior without this fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant