[Bug]: Provider v5.8.0 breaks aws_mq_broker data source

[jcmcken]

Terraform Core Version

1.5.0

AWS Provider Version

5.8.0

Affected Resource(s)

aws_mq_broker (data)

Expected Behavior

When you look up an MQ broker using the data source, it succeeds without error and you can access the attributes of that resource.

Actual Behavior

When you look up an MQ broker, you get an error in one of either the plan or apply stages, depending:

Error: setting user: Invalid address to set: []string{"user", "somedigits", "replication_user"}

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

data "aws_mq_broker" "broker" {
  broker_name = "somebroker"
}

Steps to Reproduce

Provision an MQ broker using aws_mq_broker then try to look up its attributes using the data source with the same name

Debug Output

No response

Panic Output

No response

Important Factoids

See PR #32454

I suspect that resource is updated to add a new attribute, but the data source was not, so they're out of sync.

Perhaps there should be some kind of automated CI check for this type of issue?

References

No response

Would you like to implement a fix?

No

[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.

[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.