SubnetGatewayIPV6Address and IPv6SubnetCIDRBlock metadata for IPv6-only tasks #4649
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR makes the following two changes to task metadata returned for IPv6-only awsvpc mode tasks.
SubnetGatewayIPV6Addressfield will be returned. Its value will be the subnet gateway IPv6 address used to create the default route for the task.IPv6SubnetCIDRBlockfield will be computed based on the actual subnet prefix length instead of the hardcoded/64that is used for dual-stack tasks today.Testing
IPv6-only subnet with
/64prefix -IPv6-only subnet with
/60prefix -Dual-stack subnet with
/60prefix (prefix gets hardcoded as /64 and SubnetGatewayIPv6Address is not populated) -New tests cover the changes: yes
Description for the changelog
Enhancement: SubnetGatewayIPV6Address and IPv6SubnetCIDRBlock metadata for IPv6-only tasks
Additional Information
Does this PR include breaking model changes? If so, Have you added transformation functions?
No
Does this PR include the addition of new environment variables in the README?
No
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.