Upload files to a Huwaei Blob Storage.

Parameters:

Parameters:
See dedicated page for more information.
Upload a local file to a Huawei Object Storage Service (OBS) bucket.
Supports large uploads through multipart transfer (configurable chunk size, up to 5 000 MB per part), automatic retries, and detailed debug logging. Works both on direct internet connections and through an HTTP proxy (see Configuration).
What this action does
HuaweiOBSUploadFile pushes a file from your local runtime (server, desktop, or container) to a specified OBS bucket/key. If the destination key already exists, OBS semantics apply: the object is replaced by the newly uploaded content.
How uploading works
For small files the action performs a straightforward upload. For large files it switches to multipart upload: the file is cut into parts of size chunkSz MB (up to 5 000 MB / part, which aligns with OBS limits). Parts are uploaded in sequence; if a transient failure happens, the action retries up to nRetry times before failing and applying the selected Error Management policy.
When to use it
writeReport) into cloud storage.Tip
The remote object name (idFileRemote) defines the full path inside the bucket (e.g.,reports/2025/out.docx). If you leave it empty, the action uploads using just the local file’s base name.
You need four OBS credentials/settings:
You already have step-by-step screenshots and instructions in the HuaweiOBSListFiles documentation. Follow those to create a bucket and generate AK/SK, then come back here.
Provide the file path from an upstream action (e.g., an InlineTable with a FilePath column).
Open HuaweiOBSUploadFile and set:
FilePath column.(Optional) Set idFileRemote if you want a different object name (e.g., reports/out.docx).
(Optional) Tune chunkSz (e.g., 50–200 MB for stable networks; larger for very big files).
Choose idErrorManagement:
Run the pipeline. On success, your object appears in the bucket at the specified key.
idFile pointing to /path/to/local/myfile.pdf.idFileRemote to inbox/daily-report.pdf.s3://<bucket>/inbox/daily-report.pdf.idFile must be readable from the agent that runs the pipeline. Use absolute paths where possible.idFileRemote to keep history.chunkSz to reduce the number of parts; for unstable links, smaller parts can help retries succeed.nRetry only covers transient network issues. Authentication or region mismatches fail immediately.idFileRemote empty—OBS used the local filename. Set idFileRemote to a full key like folder/name.ext.