-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
r/security_group: improve PR #1587 to fix issue #2069 #3628
Conversation
Can you please fix the
|
The logic in PR #1587 has some flaws with regards to how the security group API works in relation with TF. The problem will not show itself when you manage everything properly from TF, but when someone makes a manual change directly in AWS you could be hit by the problem described in issue #2069. This PR aims to fix that problem. As for the code itself, it does look like it’s not really DRY, but if you look closely the code is slightly different every time. So making an abstraction seems questionable in this case…
Whoops 😳Yes, of course! I amended the changes to |
Thanks for fixing this. |
Hey @svanharmelen I just realized I completely forgot about this PR and went ahead and merged a similar fix in #4416. 😓 I am really sorry about that. The maintainers here want to ensure everyone gets fair credit and this was my fault. The worst part is that your fix here was likely on the right track, if not completely correct. I'll give you a shout out for your efforts for all the tickets that are hopefully getting closed. If you have anything specific you would like to see done, please let me know and I'll personally make sure it gets some top priority attention. Thank you again for submitting this and sorry it did not get a proper review beforehand. |
Stuff happens, no worries! 👍 |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
The logic in PR #1587 has some flaws with regards to how the security group API works in relation with TF.
The problem will not show itself when you manage everything properly from TF, but when someone makes a manual change directly in AWS you could be hit by the problem described in issue #2069.
This PR aims to fix that problem. As for the code itself, it does look like it’s not really DRY, but if you look closely the code is slightly different every time. So making an abstraction seems questionable in this case…
FYI: I've updated one unit test to represent and test the updated logic and run all related acceptance tests to make sure the PR works as expected.