-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Bump moto-ext to 4.2.9.post2 #9624
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
c4f9ff7 to
5292c99
Compare
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 for the S3 part!
alexrashed
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.
The changes are looking good to me! But please make sure to get a green ext it before merging, even if it was a flake (please rerun, or make sure this is fixed first).
|
It would be great if we could get the fix for using new botocore versions into the next moto upgrade: getmoto/moto#7030 |
|
FYI: this change in moto will break instance creation for docdb + neptune |
|
Thanks for the tip @steffyP. This checks out with failures in the -ext CI: I've created a patch in moto-ext localstack/moto#72 and will release it as 4.2.9.post2 |
Brings in:
cc: @dfangl
Ext Integration Tests # 3632 🟢