Open sgreathouse-rgare opened 1 week ago
Any progress / ETA?
BTW, it appears that the 2.0.15 release has the same issue
Hello @sgreathouse-rgare, thanks for raising the issue. There was no link between your issue and 2.0.15 release. I analysed it this week and I'm working on it. Once tested, I will create a PR, possibly in a couple of days.
@acelebanski I just re-tested & 2.0.15 will not attach multiple security groups to an ENI either.
Describe the bug
https://registry.terraform.io/modules/PaloAltoNetworks/swfw-modules/aws/latest/submodules/asg
I'm passing a list of security groups for each of the 3 interfaces for a NGFW. The Lambda function only attaches the first SG to the interfaces.
I tried passing the subnet_ids & security_group_ids arguments to the lambda in the main module call in addition to passing them in the interfaces block. That resulted in the instance only having one interface. subnet_ids & security_group_ids is not really documented, so some understanding of how they function would be helpful as well.
I also noticed that the interfaces_config environment variable passed to Lambda only receives information for the mgmnt index1 & public index 2 interfaces. Maybe a clue, maybe as-designed.
Thanks for your help.
full module call.
Module Version
3.0.0-rc.1
Terraform version
Terraform v1.9.7 on linux_arm64 + provider registry.terraform.io/hashicorp/archive v2.6.0 + provider registry.terraform.io/hashicorp/aws v5.70.0 + provider registry.terraform.io/hashicorp/local v2.5.2 + provider registry.terraform.io/hashicorp/null v3.2.1
Expected behavior
multiple security groups per interface
Current behavior
one security groups per interface
Anything else to add?
No response