Add support for generating plural datasources

[rileykarson]

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. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Plural datasources are datasources that call the list endpoint of a resource and return a set of resources. They're most often used for filtering a subset of resources within a project such as those with a certain enum set.

Team thoughts:

• This should be done on an opt-in basis.
• Filtering differs between APIs. We either need custom support (preferred) or to do it clientside.
• Ideally, the resources should be returned in a stable order

New or Affected Resource(s)

• google_service_resources, eg:
  • google_compute_addresses
  • google_sql_database_instances

Potential Terraform Configuration

data "google_compute_global_addresses" "nat" {
  filter = "purpose=NAT_AUTO AND users:(/${google_compute_router.router.name})"
}

References

• Cloud DNS: Get IP for dns_policy  #3753
• NAT gateway with nat_ip_allocate_option=AUTO, no ip address output #7469
• Datasource google_sql_database_instances #8164