"aws_elasticache_user" produces perpetual diff for "access_string" and fails during apply

[vynaloze]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v1.0.0
+ provider registry.terraform.io/hashicorp/aws v3.51.0

Affected Resource(s)

• aws_elasticache_user

Terraform Configuration Files

resource "aws_elasticache_user" "this" {
  user_id       = "foo"
  user_name     = "foo"
  engine        = "REDIS"
  access_string = "on allkeys allcommands"
  passwords     = ["muchsecretpasswordwow"]
}

Debug Output

Please obtain debug output by yourself, this is trivial to reproduce.

Normal output during second apply without code changes:

Terraform will perform the following actions:

  # aws_elasticache_user.this will be updated in-place
  ~ resource "aws_elasticache_user" "this" {
      ~ access_string        = "on ~* +@all" -> "on allkeys allcommands"
        id                   = "foo"
        tags                 = {}
        # (7 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.
aws_elasticache_user.this: Modifying... [id=foo]
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to aws_elasticache_user.this, provider "provider[\"registry.terraform.io/hashicorp/aws\"]" produced an unexpected new value: Root resource was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Expected Behavior

No difference should be found. Even then, apply should not fail.

Actual Behavior

Perpetual difference is found. Apply fails.

Steps to Reproduce

1. terraform apply
2. terraform apply again

[github-actions]

This functionality has been released in v3.52.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!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.