-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
false positive: missing EIP association resources associated with NAT Gateways #1616
Comments
Moving the AwsNatGatewayEipAssoc middleware after EipAssociationExpander has not resolved the issue.
|
This was referenced Feb 1, 2023
fixed by #1619 |
This issue has been referenced in the v0.39.0 release. |
2 similar comments
This issue has been referenced in the v0.39.0 release. |
This issue has been referenced in the v0.39.0 release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
driftctl/pkg/middlewares/aws_nat_gateway_eip_assoc.go
Line 44 in 5f863c7
Results in missing resources being reported:
If I stop managing the corresponding eips, then the missing eipassocs go away, and instead I get aws_eip resources reported as not managed by IaC:
If I manage both the eip and the eipassoc, I just get a more detailed missing resource report:
Environment
How to reproduce
Allocate an EIP
Create a nat gateway and associate the EIP.
Possible Solution
Don't ignore EIP associations to nat gateways.
Additional context
The issue is probably caused by aws_eip_association_expander.go expanding the association from the eip after they were already ignored.
The text was updated successfully, but these errors were encountered: