-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
async signing support #659
Conversation
with the changes as-is we support the simple testcase I list in #658 |
This'll help with #707 (and terricain/aioboto3#173) as we essentially want to make botocore.utils.S3RegionRedirector.redirect_from_error async |
I'm going to try working on this this weekend |
@thehesiod hows it going? |
@terrycain under a mountain of work with new baby almost here 🤯 :) |
Np man, congrats 😄 |
I am very interesting in async generate_presigned_url, how I can help to merge this PR? |
hello @stalkerg , you can take a look at this PR. We need to change |
# Conflicts: # aiobotocore/client.py # aiobotocore/endpoint.py # aiobotocore/session.py # tests/test_patches.py
not sure how this happened, but we're out of sync with botocore, I'm working on cleaning this up |
This pull request introduces 4 alerts when merging 8b055ee into 957c91b - view on LGTM.com new alerts:
|
omg, the whole credentials file needs to be ported! I give up for awhile again, so much work! |
This pull request introduces 5 alerts and fixes 1 when merging d43ff58 into 904332b - view on LGTM.com new alerts:
fixed alerts:
|
ok, I think we're good in terms of emitters, now to fix tests again |
This pull request introduces 5 alerts and fixes 1 when merging b9dd4f3 into 904332b - view on LGTM.com new alerts:
fixed alerts:
|
ok fixed tests, and set |
This pull request introduces 5 alerts and fixes 1 when merging 7177429 into 904332b - view on LGTM.com new alerts:
fixed alerts:
|
Ok so according to something I read in the botocore source/docs somewhere, everything is supposed to call get_frozen_credentials, lemme have a look |
Yeah I think were good. So tests are failing because of an old pyyaml version having a CVE, pretty sure aws-cli is the culprit as they seem to have moved to using ruamel.yaml. Should we just do the usual bump botocore version stuff here and then merge? |
Also tests run fine for me so the access_key changes are good |
ya lets bump and merge! We're hitting this CVE at work too so bump would be awesome, if you don't get to in in a few hours I'll do it and merge. 🎆 🍾 |
ok doing it now |
This pull request introduces 5 alerts and fixes 1 when merging 5b61a6c into 904332b - view on LGTM.com new alerts:
fixed alerts:
|
Yay 😄 |
@terrycain thanks so much for your help! Wouldn't have been possible without you, at least for a long time :] |
No problem ;-). Just realized we need to override session._set_credentials() as otherwise it breaks when access and secret key are passed explicitly :(. Will pr in morning if you don't get there first, am too tired now :D |
Hmm I left the set, just not the get. Too tired to look now too though :) |
This starts the large work of supporting #619
Large changes:
create_client
is now a required async context classgenerate_presigned_url
is now an async callCredentials.[access_key/secret_key/token]
now raise NotImplementedError because they won't call refresh like botocore. Instead should use get_frozen_credentials async methodIn general, this is going to increase our footprint significantly.
TODO
events.emit
calls have been properly wrapped (all the way up call chain)botocore.utils.S3RegionRedirector.redirect_from_error