-
Notifications
You must be signed in to change notification settings - Fork 32
🐛lock botocore<1.36.0 until CEPH S3 is updated to be compatible with AWS S3 #7587
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
🐛lock botocore<1.36.0 until CEPH S3 is updated to be compatible with AWS S3 #7587
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7587 +/- ##
==========================================
+ Coverage 87.69% 89.06% +1.37%
==========================================
Files 1774 1245 -529
Lines 68426 52706 -15720
Branches 1125 218 -907
==========================================
- Hits 60006 46945 -13061
+ Misses 8113 5692 -2421
+ Partials 307 69 -238
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
04a5e4a to
5d03e42
Compare
|
…le with AWS S3 (ITISFoundation#7587)" This reverts commit 1b6b386.
…le with AWS S3 (ITISFoundation#7587)" This reverts commit 1b6b386.



What do these changes do?
our CEPH S3 is not 100% compatible anymore (or at least for our use) anymore with AWS S3 since botocore 1.36.0 was released this year.
Until CEPH is updated botocore version is locked which has implications on many other libraries.
this is now constrained on storage and dask-sidecar services which are the only one uploading data to S3 at this time.
The current CEPH S3 is incompatible with botocore, the AWS CLI, and any other tools based on botocore (which is almost everything)
Highlights on updated libraries (only updated libraries are included)
storage⬆️
storage⬆️🧪
storage⬆️🧪
storage⬆️🧪
Legend:
Related issue/s
How to test
Dev-ops checklist