Allow "status" filtering in "aws_ram_resource_share" datasource.

[mkielar]

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 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

When a RAM Share is deleted it remains "visible" to API Calls for a long period of time. Even worse, when the RAM Share gets replaced by terraform (e.g. as a result of #25156), the old and new RAM Shares have the same name and tags, and are practically indistinguishable to the aws_ram_resource_share datasource.

Thus, the proposal to:

1. Either, allow "status" filtering in "aws_ram_resource_share" datasource, so we could only pick Active ones,
2. Or, filter out Deleted RAM Shares to prevent Multiple resource shares found for: <name> errors.

New or Affected Resource(s)

• aws_ram_resource_share

Potential Terraform Configuration

data "aws_ram_resource_share" "this" {
  count    = local.tg_enabled
  provider = aws.network

  name           = local.transit_gateway_share
  resource_owner = "SELF"

  status = "Active"
}

References

• Breaking change in "aws_ram_resource_share" introduced in 4.17.0 #25156
• AWS RAM Share doesn't provide ability to add permissions #20499

[github-actions]

This functionality has been released in v4.18.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.