hashicorp/terraform-provider-aws

[Docs]: quicksight_data_source

Open

#41,672 opened on Mar 5, 2025

View on GitHub
 (4 comments) (2 reactions) (0 assignees)Go (10,310 forks)github user discovery
documentationgood first issueservice/quicksight

Repository metrics

Stars
 (11,045 stars)
PR merge metrics
 (PR metrics pending)

Description

Documentation Link

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/quicksight_data_source#rds-argument-reference

Description

In the latest version of the Terraform AWS provider, the value for instance_id in the aws_quicksight_data_source resource is incorrectly described.

Currently, the documentation states that instance_id refers to the instance ID of an RDS database:

[instance_id](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/quicksight_data_source#instance_id-2) - (Optional) The instance ID to which to connect.

However, in practice, Terraform expects the RDS Identifier (not the instance ID).

To prevent confusion, the documentation should be updated to:

[instance_id](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/quicksight_data_source#instance_id-2) - (Optional) The instance Identifier to which to connect.

This clarification would align the documentation with the actual expected value and help avoid misconfiguration.

References

No response

Would you like to implement a fix?

None

Contributor guide

Research direction
Inspect the documentation source for 'aws quicksight data source' in the Terraform AWS provider. Find the 'instance id' argument description, verify the expected value by examining the provider code, and update the doc to say 'instance Identifier' instead of 'instance ID'. Ensure no other references need updating.
Tech stack
go
Domain
backend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85