Repository navigation
S3: Use the seeded random for multipart upload IDs - #10553
Open
akaab-landr wants to merge 3 commits into
Open
akaab-landr wants to merge 3 commits into
akaab-landr wants to merge 3 commits into
Conversation
FakeMultipart drew its UploadId from os.urandom, so seeding Moto through /moto-api/seed did not make it reproducible. Use mock_random, as the other generated IDs already do.
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.
create_multipart_upload()draws its UploadId fromos.urandom, so the ID changes between runs even after seeding Moto with/moto-api/seed:This PR uses
mock_random, as other generated IDs already do.Test:
test_multipart_upload_ids_follow_the_seed.