fix(ec2): Fix transit gateway route table propagation filtering #8880
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.
A LocalStack user reported a 500 Internal Error when using the
GetTransitGatewayRouteTablePropagationsAPI with filters. The error occurred because the code treatedroute_table_propagationas a dictionary when it's a list of dictionaries.This PR fixed the filtering function, improved route table propagation iteration, and implemented multi-criteria resource matching. The solution was tested manually with AWS CLI, though the current tests are passing.