[Bug]: aws_opesearch_domain data source not working in 1.40.0 release

[wildk1w1]

Terraform Core Version

1.6.3

AWS Provider Version

5.40.0

Affected Resource(s)

data aws_opensearch_domain

Expected Behavior

Data source will return a correct data block as per the documentation

Actual Behavior

An error is returined.

Relevant Error/Panic Output Snippet

Error: setting auto_tune_options: Invalid address to set: []string{"auto_tune_options", "0", "use_off_peak_window"}

Terraform Configuration Files

data "aws_opensearch_domain" "local_domain" {
provider = aws.master
domain_name = "${var.environment}-elk"
}

Steps to Reproduce

Use AWS version 1.40.0 to get the bug.
Roll back to 5.39.1 and the bug goes away.

Debug Output

http.response.header.x_amzn_requestid=8accff94-4235-4664-a111-2293abce6909 rpc.method=DescribeDomainConfig rpc.system=aws-api tf_data_source_type=aws_opensearch_domain aws.region=us-west-2 http.response.header.content_type=application/json rpc.service=OpenSearch tf_req_id=3cded91b-e7c4-8fcc-dc0e-2e76134ef29e @module=aws http.response_content_length=5323 tf_mux_provider="*schema.GRPCProviderServer" tf_rpc=ReadDataSource http.duration=49 http.response.header.date="Mon, 11 Mar 2024 02:26:41 GMT" http.status_code=200 tf_aws.sdk=aws-sdk-go tf_provider_addr=registry.terraform.io/hashicorp/aws timestamp=2024-03-11T02:26:41.801Z
2024-03-11T02:26:41.802Z [ERROR] provider.terraform-provider-aws_v5.40.0_x5: [ERROR] setting state: Invalid address to set: []string{"auto_tune_options", "0", "use_off_peak_window"}
2024-03-11T02:26:41.802Z [ERROR] provider.terraform-provider-aws_v5.40.0_x5: Response contains error diagnostic: diagnostic_severity=ERROR @caller=github.com/hashicorp/[email protected]/tfprotov5/internal/diag/diagnostics.go:58 diagnostic_detail="" diagnostic_summary="setting auto_tune_options: Invalid address to set: []string{"auto_tune_options", "0", "use_off_peak_window"}" tf_data_source_type=aws_opensearch_domain tf_req_id=3cded91b-e7c4-8fcc-dc0e-2e76134ef29e tf_rpc=ReadDataSource tf_proto_version=5.4 @module=sdk.proto tf_provider_addr=registry.terraform.io/hashicorp/aws timestamp=2024-03-11T02:26:41.801Z

Panic Output

No response

Important Factoids

No response

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.

[xfournet]

please tag as a regression. I would like to avoid the same situation than with #26668 where it need many months to have the regression fixed

This issue has probably introduced by #36067

[acwwat]

@xfournet Thanks for reporting the problem and apologies for introducing the error to the data source. I am working on a fix and will complete a PR shortly after validation.

[xfournet]

Thanks for the fast resolution!

[github-actions]

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