The Azure direct (or eventual-less) template allows direct uploading to Azure, bypassing the eventual upload mechanism. For more information, see Direct (Eventual-less) versus Eventual Upload Mechanism.
The following example shows a template modified to support Azure direct upload.
<config version="3"> <chain template="azure-blob-storage-direct"/> <provider type="cache-fs" id="cache-fs"> <cacheProviderDir>/var/opt/jfrog/artifactory/data/cache</cacheProviderDir> <maxCacheSize>10000000000</maxCacheSize> </provider> <provider id="azure-blob-storage" type="azure-blob-storage"> <accountName>myaccount</accountName> <accountKey>somekey</accountKey> <endpoint>https://artifactoryhaprod.blob.core.windows.net/</endpoint> <containerName>mycontainer</containerName> <multiPartLimit>256000000</multiPartLimit> <multipartElementSize>100000000</multipartElementSize> </provider> </config>
What's in the template?
The following snippet shows the default chain that uses azure-blob-storage-direct
as the binary provider:
<config version="1"> <chain> <!-- template="azure-blob-storage-direct" --> <provider id="cache-fs" type="cache-fs"> <provider id="azure-blob-storage" type="azure-blob-storage"/> </provider> </chain> </config>
For details about the cache-fs provider, see Cached Filesystem Binary Provider.