-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/aws: Fix security group rule import #13630
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks! I was able to see the behavior described by using TestAccAWSSecurityGroup_importIPRangeAndSecurityGroupWithSameRules
and playing with removing bits from state and trying to import them, and then verify the behavior after this patch, so big thanks for including that 😄
Verified all the tests pass too, for posterity:
|
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. |
Fixes #8166 and #8827
The issue was being caused when the same rules were applied to both IP ranges and security groups. The previous implementation would combine them into a single rule, which according to the docs is not allowed. This fix creates a separate rule for each case.