-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
implemented phone ops, added tests #13449
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
Test Results - Alternative Providers202 tests - 1 261 158 ✅ - 726 2m 10s ⏱️ - 36m 6s Results for commit bdd3c30. ± Comparison against base commit c603057. This pull request removes 1265 and adds 4 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
Test Results (amd64) - Integration, Bootstrap 5 files ± 0 5 suites ±0 1h 28m 22s ⏱️ - 1h 12m 23s Results for commit bdd3c30. ± Comparison against base commit c603057. This pull request removes 2366 and adds 4 tests. Note that renamed tests count towards both.This pull request removes 386 skipped tests and adds 3 skipped tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 0m 56s ⏱️ - 1h 3m 18s Results for commit bdd3c30. ± Comparison against base commit c603057. This pull request removes 2016 and adds 4 tests. Note that renamed tests count towards both.This pull request removes 223 skipped tests and adds 3 skipped tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
bentsku
left a comment
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.
LGTM, nice implementing those methods! I just have a question regarding the expected usage of those operations, and if we're planning any follow up to allow users to actually use those methods?
In its current form, it seems pretty much hardcoded to an empty list. It doesn't have to be implemented now, I suppose there were some hardcoded values in Moto before?
In any case, one small nit would be to set that value name to lowercase if it's not a constant 👍
|
|
||
| TAGS: TaggingService = CrossRegionAttribute(default=TaggingService) | ||
|
|
||
| PHONE_NUMBERS_OPTED_OUT: list[PhoneNumber] = CrossRegionAttribute(default=list) |
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.
question: is this in uppercase because it is supposed to be a constant? if that's the case, does it make sense to be in the store?
if it's not a constant, then maybe it could be a lowercase variable
| # | ||
| # Phone number operations | ||
| # | ||
|
|
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.
question about PHONE_NUMBERS_OPTED_OUT, how are users expected to add values to that? In its current form, using an empty list would have the same result, is that right?
Are we expecting to add a new internal route in the future to allow users to add values to this field? if yes, maybe putting it back to lowercase would make sense
|
|
||
| @markers.aws.manual_setup_required | ||
| @pytest.mark.skipif(is_sns_v1_provider(), reason="Not correctly implemented in v1") | ||
| def test_is_phone_number_opted_out( |
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.
nice work validating those tests 👌
Motivation
This PR adds phone number operations in regards to opting out to SNS. The main challenge was to test this against AWS, since many restrictions apply and a phone number can only be opted back in once every 30(!) days
Closes PNX-87
Changes
opt_in_phone_number,list_phone_numbers_opted_out,check_if_phone_number_is_opted_outTests
Related