[Bug]: Typo in Quicksight Pie Chart flattenDataLabelOptions ( 'measure_visibility' -> 'measure_label_visibility' )

[MichaelYoung0705]

Terraform Core Version

1.5.3

AWS Provider Version

5.9.0

Affected Resource(s)

aws_quicksight_dashboard

Expected Behavior

For a Pie Chart visual, be able to set the 'Show Metric' option

Actual Behavior

Exception is thrown when after the resources are created, and state is being written.

Relevant Error/Panic Output Snippet

Error: setting definition: Invalid address to set: []string{"definition", "0", "sheets", "0", "visuals", "0", "pie_chart_visual", "0", "chart_configuration", "0", "data_labels", "0", "measure_visibility"}

Terraform Configuration Files

resource "aws_quicksight_dashboard" "example" {
  dashboard_id        = "example"
  name                = "example"
  version_description = "1"
  source_entity {
    source_template {
      arn = "arn:aws:quicksight:us-east-1:1111111111111:template/test/version/1"
      data_set_references {
        data_set_arn         = "arn:aws:quicksight:us-east-1:1111111111111:dataset/test"
        data_set_placeholder = "incidentals_stats"
      }
    }
  }
}

Steps to Reproduce

Create a simple analysis with one pie chart visual tied to a test DataSet with numbers.
Under the Data Labels settings, check the 'Show Metric' option.
Plan and Apply and the dashbooard will create, but throw the error while getting state ready to write.

Debug Output

In the current 5.9.0, the bug is in visual.go on line 1479. Compared to the sister method, expandDataLabelOptions() and the schema in dataLabelOptionsSchema(), "measure_visibility" should be "measure_label_visibility".

Panic Output

Error: setting definition: Invalid address to set: []string{"definition", "0", "sheets", "0", "visuals", "0", "pie_chart_visual", "0", "chart_configuration", "0", "data_labels", "0", "measure_visibility"}

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.

[justinretzolk]

Hey @MichaelYoung0705 👋 Thank you for taking the time to raise this! I'm working on a pull request that will resolve this 👍

[github-actions]

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