Copy over the ContentType of source blob for storage-encrypted blobs … #104
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.
…that are not handled by the packager
Description
Some blobs in input assets are directly copied over to destination folder, such as .json file, thumbnail file etc.
When they are not encrypted with customer's key, the code can transfer the headers from source blob to destination,
When they are encrypted with customer's key, this new change ensures the ContentType header is transfered to the destionation folder,
so that ContentType property is always available for all blobs in the destination folder.