Actions7
- Container Actions
- Blob Actions
Overview
This node allows interaction with Azure Blob Storage, specifically managing containers and blobs within an Azure storage account. The "Delete" operation on the "Blob" resource enables users to delete a specified blob from a given container. This is useful for cleaning up storage by removing files that are no longer needed or managing storage costs by deleting obsolete data.
Practical examples include:
- Automatically deleting temporary files after processing.
- Removing outdated backups or logs stored as blobs.
- Managing user-uploaded content by deleting files upon user request.
Properties
| Name | Meaning |
|---|---|
| Container Name | The name of the Azure storage container where the target blob resides. |
| Blob Name | The name (including any folder path) of the blob to be deleted, e.g., folder/file.txt. |
Output
The output is a JSON array containing the results of the delete operation for each input item. Each element corresponds to one deletion attempt and includes information about whether the blob was successfully deleted.
Specifically, the output contains the raw response from the Azure SDK's deleteIfExists method, which indicates if the blob existed and was deleted. No binary data is outputted by this operation.
Dependencies
- Requires an Azure Storage API credential with a valid connection string to authenticate against Azure Blob Storage.
- Uses the official Azure Storage Blob SDK (
@azure/storage-blob) internally. - The node expects the connection string to contain both the account name and key.
Troubleshooting
Common issues:
- Invalid or missing container or blob names will cause the operation to fail.
- If the provided connection string is invalid or lacks necessary permissions, authentication errors will occur.
- Attempting to delete a non-existent blob will not throw an error but will indicate the blob did not exist.
Error messages:
- Errors related to undefined or malformed connection strings indicate misconfiguration of credentials.
- Permission-related errors suggest insufficient rights on the Azure Storage account.
- If the blob name or container name is empty or incorrect, the Azure SDK may throw errors indicating resource not found.
To resolve these:
- Verify the container and blob names are correct and exist.
- Ensure the Azure Storage API credential is properly configured with a valid connection string.
- Confirm the credential has sufficient permissions to delete blobs.