[Bug]: MSK Cluster Configuration change to infinite retention

[aidan-melen]

Terraform Core Version

1.3.x

AWS Provider Version

4.30.0

Affected Resource(s)

• aws_msk_cluster
• aws_msk_configuration

Expected Behavior

We should be able to set log.retention.ms=-1 in the aws_msk_configuration

Actual Behavior

Provider produced inconsistent final plan

Relevant Error/Panic Output Snippet

│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for module.aws_msk_blue[0].aws_msk_cluster.this[0]
│ to include new values learned so far during apply, provider
│ "registry.terraform.io/hashicorp/aws" produced an invalid new value for
│ .configuration_info[0].revision: was cty.NumberIntVal(1), but now
│ cty.NumberIntVal(2).
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.

Terraform Configuration Files

We are using a custom module that passes config values to the aws_msk_configuration resource

Steps to Reproduce

create an msk cluster with log.retention.ms=10000000 set to an integer. apply update an msk cluster with log.retention.ms=-1. apply

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

No

[github-actions[bot]]

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.