Ignore propagated routes during table import #5100
Merged
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.
Similar to how they're ignored when performing a
resourceAwsRouteTableRead
.Relates to #5099
This syncs the continue logic from resourceAwsRouteTableImportState and resourceAwsRouteTableRead. Really these should be using a helper function, but given there's already 3 other places with this code copy-pasted, I wasn't sure what the preferred way of doing this would be. Writing a test for this seems like it'd be pretty difficult, since a full test would require a gateway connected that has routes propagating into it. I assume that's why the existing resourceAwsRouteTableRead doesn't have a comparable test.
Output from test runs below. Apologies I don't have AWS creds in place that I can run this test against. The change proposed here is rather trivial though, and this at least shows it compiles / passes existing normal tests.