-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Error with creating same ipv6 rule when using multiple *_with_source_security_group_id #79
Comments
Thanks for opening this issue. You are right, this use-case is not supported by this module, and to be honest, I don't see how it can be implemented right now. hashicorp/terraform#2376 - this has more details. Ideas and PRs are welcome. |
Please use v3.6.0 which has been just released. |
Thanks, @JoshiiSinfield, for the advice! I've separated SG rules to different resources/modules. In my case issue was related to ingress rows with the same ports but different protocol
|
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. |
Hi,
the following code:
produces the following error:
Error message: the specified rule "peer: ::/0, TCP, from port: 3306, to port: 3306, ALLOW" already exists
adding this:
egress_ipv6_cidr_blocks = []
fixes the issue, however I no longer get ipv6 CIDRs.the working is fine for us as we don't currently use ipv6 however I can see it being an issue others.
Cheers,
Josh
The text was updated successfully, but these errors were encountered: