ipv4_network_definition is not a managed PL

[dbillon]

Hello,

From this module documentation:

The variable var.ipv4_network_definition is an attribute to configure a supernet (IPv4 CIDR block) or managed prefix list of your network/VPCs in AWS.

But it seems that the module consider var.ipv4_network_definition as an AWS Prefix List: from modules/egress_vpc:

data "aws_prefix_list" "ipv4_network_definition" {
  count = startswith(coalesce(var.ipv4_network_definition, " "), "pl-") ? 1 : 0

  prefix_list_id = var.ipv4_network_definition
}

Thus it can't find a customer managed Prefix Lists.

BR,

Damien.

[pablo19sc]

Hi!

Thanks for your comment.

I don't fully understand your question here. What are you trying to achieve and what's the error?

That variable expects either a list of CIDRs or a customer-managed prefix list (in case you don't have a contiguous block that you define in a supernet). This variable is used in the corresponding VPCs (mainly the egress/ingress ones) to route to the Core Network.

Regards,
Pablo

[dbillon]

Hi Pablo,

I used a workaround but from what I remember, if I put a Customer-managed prefix list in ipv4_network_definition I get an error.

It seems due to the fact that the "egress_vpc" module looks up this var from the aws_prefix_list Terraform resource. I guess that it should also try to find this prefix list from aws_ec2_managed_prefix_list Terraform resource. Terraform publishes different resources for Customer-managed prefix lists and for AWS-managed prefix lists.

Hope this helps.

BR, Damien.

[pablo19sc]

Oh I see. Can you provide an example of code that gives the error? To fully test exactly the same example you were checking, and see if it's something we need to check as functionality or simply a bug.