-
Notifications
You must be signed in to change notification settings - Fork 342
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
ec2_vpc_route_table should support IPv6 routes #768
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Hi @vonschultz, Thanks for taking the time to raise this issue. IPv6 support was added by #601 and should be available with release 3.1.0 of amazon.aws. |
Files identified in the description:
If these files are inaccurate, please update the |
Ah, nice! |
I've now upgraded to
I see the corresponding code in main, https://github.com/ansible-collections/amazon.aws/blob/main/plugins/modules/ec2_vpc_route_table.py, function I'm fine with skipping purging this route, as the |
elb_instance - initial integration tests SUMMARY Rewrite elb_instance (ec2_elb) for boto3 ISSUE TYPE Feature Pull Request COMPONENT NAME elb_instance ADDITIONAL INFORMATION fixes: ansible-collections#384 Reviewed-by: Markus Bergholz <[email protected]> Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
elb_instance - initial integration tests SUMMARY Rewrite elb_instance (ec2_elb) for boto3 ISSUE TYPE Feature Pull Request COMPONENT NAME elb_instance ADDITIONAL INFORMATION fixes: ansible-collections#384 Reviewed-by: Markus Bergholz <[email protected]> Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
elb_instance - initial integration tests SUMMARY Rewrite elb_instance (ec2_elb) for boto3 ISSUE TYPE Feature Pull Request COMPONENT NAME elb_instance ADDITIONAL INFORMATION fixes: ansible-collections#384 Reviewed-by: Markus Bergholz <[email protected]> Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
Summary
When trying to add e.g. the default route for IPv6,
::/0
, it complains that's not a valid CIDR. When IPv6 routes are already in place, it produces warnings sayingcommunity.aws.ec2_vpc_route_table
should support IPv6 routes, and gracefully handle any IPv6 routes that are already there.Issue Type
Feature Idea
Component Name
ec2_vpc_route_table
Additional Information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: