-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
validate and add S3Control tests #10932
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
0eba42b
to
adb48c8
Compare
LocalStack Community integration with Pro 2 files ±0 2 suites ±0 1h 44m 25s ⏱️ + 3m 46s Results for commit 9bb20e8. ± Comparison against base commit c5fdfbe. This pull request removes 2 and adds 11 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
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 list of new tests!
Good to see there is still work to keep you busy too! 🤣
Just left one question regarding snapshots but it might not be relevant 😄
assert put_response["ResponseMetadata"]["HTTPStatusCode"] == 200 | ||
|
||
get_response = s3control_client.get_public_access_block(AccountId=account_id) | ||
assert access_block_config == get_response["PublicAccessBlockConfiguration"] |
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: Was there any issues with performing snapshots? Or reasoning as to why it is not needed?
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.
Oh no, this was a legacy test, I've just validated it but did not add snapshot. I think the goal would be to delete this one in favor of the newer ones created but currently skipped because the parity isn't there at all for now!
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.
👌 makes total sense!
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.
I'll add a comment on the class to clarify still! thanks 😄
Motivation
As part of the S3 Control provider migration, I had started to add more tests with #9730.
Sadly, I didn't have the time to fully go through with the migration, and we didn't get a request yet for it. I'll focus more on it if we have then, it only needs a bit more work which should be fine (+ integration with S3 itself).
But as part of validating and removing
aws.unknown
test markers, I'm already cherry picking the tests.Changes