You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
Currently GetVpcById() returns a struct with no information about the CIDR associated with the VPC.
typeVpcstruct {
Idstring// The ID of the VPCNamestring// The name of the VPCSubnets []Subnet// A list of subnets in the VPCTagsmap[string]string// The tags associated with the VPCCidrstringSecondaryCidr []string
}
I am writing a test which checks the IPv4 CIDR and secondary associations as well as IPv6, looking into GetVpcByID() it looks like it uses DescribeVpcs() which includes this information.
I could make the call to rather than using the helper functions in terratest but it would be nice to use them! I propose adding the following new fields to the vpc struct:
typeVpcstruct {
CidrBlock*string// The primary IPv4 CIDR block for the VPC.CidrAssociations*[]stringIpv6CidrAssociations*[]string
}
Bit of a rough and ready proposal but you get the idea! Would be great to get some feedback, I am happy to implement this 😄
This would allow me to quickly setup a test which is something like this:
Describe the solution you'd like
Currently
GetVpcById()
returns a struct with no information about the CIDR associated with the VPC.I am writing a test which checks the IPv4 CIDR and secondary associations as well as IPv6, looking into
GetVpcByID()
it looks like it usesDescribeVpcs()
which includes this information.https://docs.aws.amazon.com/sdk-for-go/api/service/ec2/#Vpc
I could make the call to rather than using the helper functions in terratest but it would be nice to use them! I propose adding the following new fields to the vpc struct:
Bit of a rough and ready proposal but you get the idea! Would be great to get some feedback, I am happy to implement this 😄
This would allow me to quickly setup a test which is something like this:
Thanks!
The text was updated successfully, but these errors were encountered: