Azure File Copy Task 4.*: Update to AzCopy 10.11 to support custom file extension to content-type mappings #15070
Assignees
Comments
ghost
added
the
|
Any hope of getting this in? Azure File Copy Task 4.* is still using |
2 tasks
v-jkarri
added a commit
that referenced
this issue
Dec 21, 2021
…to AzCopy 10.11 to support custom file extension to content-type mappings #15070
v-nagarajku
added a commit
that referenced
this issue
Feb 3, 2022
#15594) * 15070 #Azure File Copy Task 4.*: Update to AzCopy 10.11 to support custom file extension to content-type mapping * AzureFileCopy V4 CleanTarget #14759 Azure File Copy Task 4.*: Update to AzCopy 10.11 to support custom file extension to content-type mappings #15070 * updated readme file * Updated readme * AzureFileCopyv5 PR review changes Co-authored-by: Philipson Joseph V <77002750+PhilipsonJoseph@users.noreply.github.com> Co-authored-by: v-nagarajku <v-nagarajku@microsoft.com> Co-authored-by: v-nagarajku <96724708+v-nagarajku@users.noreply.github.com>
|
Fixed the issue with ref to the below: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AzCopy 10.11 finally adds the capability to define your own file extension -> content-type mappings using a JSON file.
If the
AZCOPY_CONTENT_TYPE_MAPenvironment variable is set to the path of a JSON file, the mappings defined in this file will take precedence over the mappings built into the operating system.https://github.com/Azure/azure-storage-azcopy/wiki/Custom-mime-mapping
With this new feature you finally get full control of the target blobs' Content-Type properties when AzCopy-ing.
I have been waiting for this AzCopy feature for more than 2.5 years (Azure/azure-storage-azcopy#136 (comment))
Please update the pipeline task to use AzCopy >= 10.11 so that this can be utilized in the Azure File Copy task.
PS! This task would also resolve #14809
The text was updated successfully, but these errors were encountered: