[Bug]: aws_lexv2models_slot resource cannot create prompt_specification

[MaxiRam]

Terraform Core Version

1.7.2, 1.7.0

AWS Provider Version

5.35.0

Affected Resource(s)

aws_lexv2models_slot

Expected Behavior

Would expect that a slot with an elicitation prompt would be created after converting the block:
value_elicitation_setting { slot_constraint = "Required" prompt_specification { max_retries = 1 message_group { message { plain_text_message { value = "A really good question" } } } } }

Actual Behavior

The Error message pasted below is shown. I'm not able to make a plan, so there is not even chance to apply

Relevant Error/Panic Output Snippet

│ Error: Unable to Convert Configuration
│ 
│   with aws_lexv2models_slot.tiempo-plan,
│   on chatbot.tf line 90, in resource "aws_lexv2models_slot" "tiempo-plan":
│   90: resource "aws_lexv2models_slot" "tiempo-plan" {
│ 
│ An unexpected error was encountered when converting the configuration from the protocol type. This is always an issue in terraform-plugin-framework used to implement the provider and
│ should be reported to the provider developers.
│ 
│ Please report this to the provider developer:
│ 
│ Unable to unmarshal DynamicValue:
│ AttributeName("value_elicitation_setting").ElementKeyInt(0).AttributeName("prompt_specification").ElementKeyInt(0).AttributeName("message_group").ElementKeyInt(0).AttributeName("message").ElementKeyInt(0):
│ unknown attribute "custom_playload"

Terraform Configuration Files

aws_lexv2models_slot.zip

Steps to Reproduce

terraform init
terraform plan

Debug Output

debug.txt

Panic Output

No response

Important Factoids

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.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. 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.

[github-actions]

This functionality has been released in v5.42.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.