
Export files to Microsoft Azure
🤖/azure/store exports encoding results to Microsoft Azure.
Keep your credentials safe
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
output_meta
Record<string, boolean> | boolean
Allows you to specify a set of metadata that is more expensive on CPU power to calculate, and thus is disabled by default to keep your Assemblies processing fast.
For images, you can add
"has_transparency": true
in this object to extract if the image contains transparent parts and"dominant_colors": true
to extract an array of hexadecimal color codes from the image.For videos, you can add the
"colorspace: true"
parameter to extract the colorspace of the output video.For audio, you can add
"mean_volume": true
to get a single value representing the mean average volume of the audio file.You can also set this to
false
to skip metadata extraction and speed up transcoding.result
boolean
(default:false
)Whether the results of this Step should be present in the Assembly Status JSON
queue
"batch"
Setting the queue to 'batch', manually downgrades the priority of jobs for this step to avoid consuming Priority job slots for jobs that don't need zero queue waiting times
force_accept
boolean
(default:false
)Force a Robot to accept a file type it would have ignored.
By default Robots ignore files they are not familiar with. 🤖/video/encode, for example, will happily ignore input images.
With the force_accept parameter set to true you can force Robots to accept all files thrown at them. This will typically lead to errors and should only be used for debugging or combatting edge cases.
use
string | Array<string> | Array<object> | object
Specifies 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" ] }
Tip
That’s likely all you need to know about
use
, but you can view Advanced use cases.- You can pick any names for Steps except
credentials
string
Please 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
The content type with which to store the file. By default this will be guessed by Azure.
content_encoding
string
The content encoding with which to store the file. By default this will be guessed by Azure.
content_language
string
The content language with which to store the file. By default this will be guessed by Azure.
content_disposition
string
The content disposition with which to store the file. By default this will be guessed by Azure.
cache_control
string
The cache control header with which to store the file.
metadata
Record<string, string>
(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
string | number
Set 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
Set this to a combination of
r
(read),w
(write) andd
(delete) for your shared access signatures (SAS) permissions.