Export files to Microsoft Azure
🤖/azure/store exports encoding results to Microsoft Azure.
Usage example
Export uploaded files to my_target_folder
on Azure:
{
"steps": {
"exported": {
"robot": "/azure/store",
"use": ":original",
"credentials": "YOUR_AZURE_CREDENTIALS",
"path": "my_target_folder/${unique_prefix}/${file.url_name}"
}
}
}
Parameters
-
use
String / Array of Strings / Object requiredSpecifies which Step(s) to use as input.
-
You can pick any names for Steps except
":original"
(reserved for user uploads handled by Transloadit) -
You can provide several Steps as input with arrays:
"use": [ ":original", "encoded", "resized" ]
💡 That’s likely all you need to know about
use
, but you can view Advanced use cases. -
-
credentials
StringrequiredPlease create your associated Template Credentials in your Transloadit account and use the name of your Template Credentials as this parameter's value. They will contain the values for your Azure Container, Account and Key.
While we recommend to use Template Credentials at all times, some use cases demand dynamic credentials for which using Template Credentials is too unwieldy because of their static nature. If you have this requirement, feel free to use the following parameters instead:
"account"
,"key"
,"container"
. -
path
String ⋅ default:"${unique_prefix}/${file.url_name}"
The path at which the file is to be stored. This may include any available Assembly variables.
-
content_type
String ⋅ default:""
The content type with which to store the file. By default this will be guessed by Azure.
-
content_encoding
String ⋅ default:""
The content encoding with which to store the file. By default this will be guessed by Azure.
-
content_language
String ⋅ default:""
The content language with which to store the file. By default this will be guessed by Azure.
-
cache_control
String ⋅ default:""
The cache control header with which to store the file.
-
metadata
Object ⋅ default:{}
A JavaScript object containing a list of metadata to be set for this file on Azure, such as
{ FileURL: "${file.url_name}" }
. This can also include any available Assembly variables. -
sas_expires_in
IntegerSet this to a number to enable shared access signatures for your stored object. This reflects the number of seconds that the signature will be valid for once the object is stored. Enabling this will attach the shared access signature (SAS) to the result URL of your object.
-
sas_permissions
String ⋅ default:""
Set this to a combination of
r
(read),w
(write) andd
(delete) for your shared access signatures (SAS) permissions.
Note: The URLs in the result JSON already point to the file on your target storage platform, so you can just save that URL in your database.
Demos
- Copy files from Backblaze to Azure
- Copy files from DigitalOcean Spaces to Azure
- Copy files from Dropbox to Azure
- Copy files from FTP servers to Azure
- Copy files from Google Storage to Azure
- Copy files from MinIO to Azure
- Copy files from Openstack/Swift to Azure
- Copy files from Rackspace Cloud Files to Azure
- Copy files from SFTP servers to Azure
- Copy files from Supabase to Azure
- Copy files from Wasabi to Azure
- Copy files from Webservers to Azure
- Copy files from cloudflare to Azure
- Store uploaded files in a Microsoft Azure container
Related blog posts
- New Azure & Softlayer storage options at Transloadit November 18, 2015
- Happy 2016 from Transloadit December 31, 2015
- New pricing model for future Transloadit customers February 7, 2018
- Introducing the /azure/store Robot for Microsoft Azure January 7, 2020