Allow data source ec2_managed_prefix_list to return more than one match

[iyesin]

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

I was trying to refer organization-wide shared prefix lists by filtering them by name. Unfortunately, my attempts failed with
│ Error: more than 1 prefix list matched the given criteria

New or Affected Resource(s)

• data.aws_ec2_managed_prefix_list

Potential Terraform Configuration

data "aws_ec2_managed_prefix_list" "prod_lists" {
  filter {
    name = "owner-id"
    values = [var.pfx_owner]
  }

  filter {
    name = "prefix-list-name"
    values = ["???_production"]
  }
}

This will match two production-related prefix lists.

References

Underlying API supports enumerating more than one resource at time. See https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeManagedPrefixLists.html .
Same works with aws-cli: aws ec2 describe-managed-prefix-lists --filter "Name=prefix-list-name,Values=???_$ENVIRONMENT" --filter "Name=owner-id,Values=$OWNER" | grep -c "PrefixListArn"

7

• #0000

[ewbankkit]

@iyesin Thanks for raising this issue.
It has already been noticed in #17119. I'm going to close this one as a duplicate so that we can concentrate discussion in the linked issue.
Please add any additional comments there.

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