-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
EC2: fix describe-availability-zones filtering #12661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 46s ⏱️ - 1h 42m 5s Results for commit a3ad991. ± Comparison against base commit bae7a0e. This pull request removes 4437 and adds 3 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
d8c0912
to
0a1d355
Compare
0a1d355
to
a3ad991
Compare
Test Results - Alternative Providers597 tests 419 ✅ 14m 59s ⏱️ Results for commit a3ad991. |
Update: After a few retries that unrelated flaky test passed. FYI: The ci check failure is unrelated to these changes: this test is failing: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A nice clean fix, LGTM!
Motivation
Customer reported some issue trying to run a tf script where they were getting this error:
Error: no matching EC2 Availability Zone found
.The reason for that is that this operation implementation in the ec2 provider.py filters doesn't work against moto, resulting into an empty list.
More context in the notion ticket.
Changes
Change how filters are passed for the call done to moto.
Added aws validated tests.
test_describe_availability_zones_filter_with_zone_names
fails against LS with the old code, and passes now.