Add a aws_rds_cluster_instance data source or add cluster type info to the aws_rds_instance data source

[digitalfiz]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Right now it is impossible to get enough info for a rds instance to know if it is a reader or writer because the aws_db_instance data source does not return things like writer=true|false.

So can we either add a new data source for aws_rds_cluster_instance or just add some more return values to aws_db_instance. i am not sure what you guys normally do when there are very similar resources with slightly different properties.

New or Affected Resource(s)

• aws_rds_cluster_instance
• aws_db_instance

Potential Terraform Configuration

Something close to what I am attempting:

data "aws_db_instance" "dbs" {
  count                  = length(module.stack.aurora_instance_ids)
  db_instance_identifier = module.stack.aurora_instance_ids[count.index]
}

output "readers" {
  value = [for i, z in data.aws_db_instance.dbs.* : z.id if z.writer == False]
}

output "writer" {
  value = [for i, z in data.aws_db_instance.dbs.* : z.id if z.wrtier == True][0]
}

This is not working code but the idea is there.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[digitalfiz]

Well that's unfortunate....

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