adds support for metadata during object creation #287
Conversation
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
CNDW
force-pushed
the
object-metadata
branch
from
6abe364 to
a9e2f4a
Compare
CNDW
force-pushed
the
object-metadata
branch
from
a9e2f4a to
d9447d0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
New objects being created via the
google.cloud.storage.Blobapi that have hadmetadataset on the object viablob.metadataare not having the metadata persisted in the emulator.The upload process from the google cloud library initiates the upload with a POST to
/b/(?P<bucket_name>)/o?uploadType=resumablewith aContent-Type: application/jsonheader themetadatastored in the payload. The emulator is pulling the object name from the payload but it is not piping the metadata through to object creation