Actions7
Overview
The node interacts with VolcEngine Cloud Object Storage (TOS/TOD) to perform various file and bucket operations. Specifically, the "Copy File" operation copies a file within the TOS storage system from one location to another. This is useful for duplicating files without downloading and re-uploading them, saving bandwidth and time.
Common scenarios include:
- Creating backups of important files within the same storage bucket.
- Duplicating files to different folders or buckets for organizational purposes.
- Preparing files for processing by copying them to specific locations.
Example: Copy a file named reports/2023-summary.pdf to archive/2023-summary-backup.pdf within the same bucket.
Properties
| Name | Meaning |
|---|---|
| File Path | The path and name of the file in TOS to be copied. For the copy operation, this is the source file path. |
Note: The provided properties JSON only defines "File Path" as input relevant to the Copy File operation. Other required parameters like destination path are likely handled internally or via additional properties not shown here.
Output
The node outputs an array of items corresponding to each input item processed. Each output item contains a json field with the result of the copy operation. The exact structure depends on the underlying SDK response but generally includes metadata about the copied file such as its new location, status, and any relevant identifiers.
No binary data output is indicated for the copy operation.
Dependencies
- Requires an API key credential for VolcEngine TOS with access permissions to perform file operations.
- Uses the official VolcEngine TOS SDK (
@volcengine/tos-sdk) for interacting with the cloud storage. - Node configuration must include valid credentials with accessKey, secretKey, region, endpoint, and bucket information.
Troubleshooting
- Missing Credentials: If no credentials are provided or invalid, the node throws an error "No credentials returned!" Ensure that the API key credential is properly configured.
- Permission Issues: Copy operation may fail if the credentials lack permission to read the source file or write to the destination path.
- Invalid File Paths: Providing incorrect or non-existent source file paths will cause errors. Verify the file path exists before copying.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON.