upgrade panda to latest; partially switching to s3 sdk v2#4737
Merged
Conversation
Contributor
|
This looks good to me on a code level! When testing in CODE though I found that I wasn't sure how the |
|
Seen on auth, usage, metadata-editor, leases, cropper, collections, media-api, kahuna (merged by @andrew-nowak 9 minutes and 59 seconds ago) Please check your changes! |
|
Seen on image-loader, thrall (merged by @andrew-nowak 12 minutes and 9 seconds ago) Please check your changes! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change?
Upgrade pan-domain-auth to latest version, which requires partially switching to the v2 s3 sdk.
How should a reviewer test this change?
How can success be measured?
Who should look at this?
Tested? Documented?