[Bug]: Quicksight YAxis data based range failed to apply

[yev-anna]

Terraform Core Version

1.5.6

AWS Provider Version

5.17.0

Affected Resource(s)

• aws_quicksight_analysis
• aws_quicksight_dashboard

Expected Behavior

YAxis is based on data range

Actual Behavior

Dashboard/analysis fails to be updated

Relevant Error/Panic Output Snippet

│ Error: updating Amazon QuickSight Dashboard (123,example): ValidationException: 1 validation error detected: Value 'AxisDisplayRange(minMax=null, dataDriven=null)' at 'definition.sheets.1.member.visuals.1.member.lineChartVisual.chartConfiguration.primaryYAxisDisplayOptions.axisOptions.dataOptions.numericAxisOptions.range' failed to satisfy constraint: Only 1 member of [minMax, dataDriven] should be provided for structure AxisDisplayRange

Terraform Configuration Files

resource "aws_quicksight_dashboard" "example_dashboard" {
  dashboard_id        = "example"
  name                = "example"
  definition {
    data_set_identifiers_declarations {
        ...
    }
    sheets {
      ...
      visuals {
        line_chart_visual {
          visual_id = "example"
          chart_configuration {
            field_wells {
              ...
            }
            primary_y_axis_display_options {
              axis_options {
                data_options {
                  numeric_axis_options {
                    range {
                      data_driven { }
                    }
                  }
                }
              }
            }
          }
        }
      }     
    }
  }
}

Steps to Reproduce

terraform init terraform plan terraform apply

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

https://docs.aws.amazon.com/quicksight/latest/APIReference/API_AxisDisplayDataDrivenRange.html

Would you like to implement a fix?

None

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