-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
S3 migration - set s3 v2 provider as default #6827
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 integration with Pro 1 files - 2 1 suites - 2 1h 7m 29s ⏱️ - 25m 55s For more details on these failures, see this check. Results for commit b0af983. ± Comparison against base commit 6e81652. ♻️ This comment has been updated with latest results. |
efa44f5
to
c7e3574
Compare
Note: we have 53 failed tests for now, to keep track of progress. |
95f7015
to
ee6e477
Compare
ee6e477
to
d63f96e
Compare
We are at 92 tests failing for this branch before merging any functionality. |
d63f96e
to
b20cb40
Compare
b20cb40
to
aa63747
Compare
b26243f
to
61fd406
Compare
61fd406
to
3fd44cc
Compare
3fd44cc
to
c68804b
Compare
c68804b
to
65c59e7
Compare
Co-authored-by: Ben Simon Hartung <[email protected]>
Co-authored-by: Ben Simon Hartung <[email protected]>
Summary
This PR should remain minimal in terms of code changes, and is mostly used for keeping track of the PRs regarding the new s3 provider going directly into master and for tracking test failure rates against the new provider.
PRs
The following PRs have been created to fully implement the new s3 provider:
Tasks
Migrate all s3 tests to pytest and validates them against AWS
Create the new ASF provider
Allow patching of botocore specs to match actual AWS behaviour
Reroute virtual host addressed requests as path addressed ones to take advantage of the builtin ASF routing
Implement major S3 features:
Fix ongoing issues with current provider not tackled in above major features
Implement the Pro provider
Implement S3 ASF test job for CircleCI