Azure Storage - Create container
Declaration
<AMAZURESTORAGE ACTIVITY="create_container" CONTAINER="text" ACCESSLEVEL="text (options)" PROTOCOL="text (options)" ACCOUNTNAME="text" ACCESSKEY="text (encrypted)" BLOBENDPOINT="text" QUEUEENDPOINT="text" TABLEENDPOINT="text" TIMOUT="number" PROXYTYPE="text (options)" PROXYSERVER="text" PROXYPORT="number" PROXYUSERNAME="text" PROXYPASSWORD="text (encrypted)"><METADATA NAME="text" VALUE="text" /><METADATA NAME="text" VALUE="text" /><METADATA NAME="text" VALUE="text" /></AMAZURESTORAGE>
Description: Creates a new public or private blob container under the specified account and optionally sets user-defined metadata for the container.
Practical Usage
Commonly used to create a new container as a means to organize sets of blobs. Blob storage containers behave like a folder in which we store files.
Connection Parameters
Property | Type | Required | Default | Markup | Description |
---|---|---|---|---|---|
Connection |
|
|
|
|
Indicates where user credentials and preferences should originate from. This is a design mode parameter used only during task construction and configuration, thus, comprises no markup. The available options are:
|
Session |
Text |
Yes if connection is session-based |
AzureStorageSession1 |
SESSION="MyAzureSession" |
The name of an existing session to associate this activity with. This parameter is active only if the Connection parameter is set to Session. The default session name is 'AzureStorageSession1'. |
Account name |
Text |
Yes if connection is host-based |
(Empty) |
ACCOUNTNAME="myaccount" |
The globally unique name of the Windows Azure storage account. This parameter is active only if the Connection parameter is set to Host. |
Access key |
Text |
Yes if connection is host-based |
(Empty) |
ACCESSKEY="[AccessKey]" |
The primary or secondary access key (each composed of 88 ASCII characters) used to authorize access to Azure Storage. This parameter is active only if the Connection parameter is set to Host. |
Protocol |
Text (options) |
No |
HTTPS |
|
The type of protocol used to access Azure Storage. The available options are:
|
Timeout (seconds) |
Number |
No |
90 |
TIMEOUT="180" |
The timeout interval (in seconds) for requests made to the storage service. If the timeout elapses before a server response is returned, the operation times out and the service returns an error. The default timeout value is 90 seconds. |
Blob endpoint URI |
Text |
No |
(Empty) |
BLOBENDPOINT="http://accnt .blob.core.windows.net" |
The endpoint for the Blob service, as configured for the Azure Storage account. The default Blob service endpoint is '[http/https]://accountname.blob.core.windows.net', where 'accountname' is the name of the Azure Storage account. |
Queue endpoint URI |
Text |
No |
(Empty) |
QUEUEENDPOINT="http://accnt .queue.core.windows.net" |
The endpoint for the Queue service, as configured for the Azure storage account. The default Queue service endpoint is '[http/https]://accountname.queue.core.windows.net', where 'accountname' is the name of the Azure Storage account. |
Table endpoint URI |
Text |
No |
(Empty) |
TABLEENDPOINT="http://accnt .table.core.windows.net" |
The endpoint for the Table service, as configured for the Azure storage account. The default Table service endpoint is Property |
Container name |
Text |
Yes |
(Empty) |
CONTAINER="mynewcontainer" |
The name of the new container to create. Within a given storage account, every container must have a unique name. Container names must conform to the following rules:
NOTE: If a container with the same name already exists, the operation fails. |
Public access |
Text (options) |
Yes |
Private |
|
Indicates the Access Control List (ACL) permissions level to set for the new container, which determine whether container data and blob resources are available for anonymous access. The available options are:
|
[Metadata] Name |
Text |
No |
(Empty) |
NAME="mymetadataname" |
The metadata name to specify for the new container. This activity supports entry of one or more user-defined name-value pairs to associate with the new container as metadata. To add a name-value pair in visual mode, select font-weight: bold;">Click here to add new row... then enter the metadata name in the font-weight: bold;">Name field and its value in the font-weight: bold;">Value field. To delete a name-value pair, click "X". |
[Metadata] Value |
Text |
No |
(Empty) |
VALUE="mymetadatavalue" |
The metadata value to associate with its associated name entered in the Name parameter. To add a name-value pair in visual mode, select font-weight: bold;">Click here to add new row... then enter the metadata name in the font-weight: bold;">Name field and its value in the font-weight: bold;">Value field. To delete a name-value pair, click "X". |
Description tab - A custom description can be provided on the Description tab to convey additional information or share special notes about a task step.
Error Causes tab - Specify how this step should behave upon the occurrence of an error. (Refer to Task Builder > Error Causes Tab for details.)
On Error tab - Specify what AWE should do if this step encounters an error as defined on the Error Causes tab. (Refer to Task Builder > On Error Tab for details.)
Example
The sample AML code below can be copied and pasted directly into the Steps panel of the Task Builder.
Description: This task creates an Azure Storage session, creates a container, updates the container, uploads a blob onto the container, and finally, ends the session.
<!-- Create session --> <AMAZURESTORAGE ACTIVITY="create_session" ACCOUNTNAME="netauto" ACCESSKEY="AM2rpq73bKmXN7UmqHdyKZZ3qCaiN3apm zen5q83eWmU967mr7d7aZs3oma592opmjeiZqF3eymLN60mpTdg6YY2g==aME" PROTOCOL="http" SESSION="MySession" /> <!-- Create container --> <AMAZURESTORAGE ACTIVITY="create_container" CONTAINER="mycontainer" ACCESSLEVEL="publiccontainer" PROVIDER="session_based" SESSION="MySession"><METADATA NAME="Data" VALUE="Documents" /></AMAZURESTORAGE> <!-- Update container --> <AMAZURESTORAGE ACTIVITY="update_container" CONTAINER="mycontainer" ACCESSLEVEL="publiccontainer" PROVIDER="session_based" SESSION="MySession"><SHAREDACCESSPOLICY NAME="mypolicy" READ="True" WRITE="True" DELETE="True" LIST="True" STARTTIME="11/13/2011 2:00:00 AM" EXPIRYTIME="11/15/2011 12:00:00 AM" /></AMAZURESTORAGE> <!-- Upload blob --> <AMAZURESTORAGE ACTIVITY="upload_blob" CONTAINER="mycontainer" FILE="C:\temp\sourceForm.pdf" PROVIDER="session_based" SESSION="MySession" /> <!-- End Session --> <AMAZURESTORAGE ACTIVITY="end_session" SESSION="MySession" />