[RM-1480] Suppress InvalidVpcID.NotFound on describe VPC classic link calls #5
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.
Why
Some VPCs incorrectly fail to refresh due to
InvalidVpcID.NotFound
.What
In some research I found a potential cause that cropped up for other people: describe VPC classic link calls can fail with this:
ansible/ansible#36083
This PR suppresses the error on
DescribeVpcClassicLink
andDescribeVpcClassicLinkDnsSupport
which are made to set the optional attributesenable_classiclink
andenable_classiclink_dns_support
.https://www.terraform.io/docs/providers/aws/r/vpc.html#enable_classiclink
The provider already suppresses
UnsupportedOperation
for both of these calls, but my suspicion is AWS may also return VPC not found in certain cases.