...
Rclone needs to be installed on the same server where the Universal Agent is installed. Rclone binary should be stored on a location where Universal Agent has access and permissions to execute it.
| Note |
|---|
This Universal Extension has been tested with Rclone v1.58.1. It should be working with later Rclone versions, as long as these are backwards compatible. |
Network and Connectivity Requirements
...
- Amazon S3
- Google Cloud Storage
- Microsoft OneDrive Business
- Local file system (Linux, Windows)
| Note |
|---|
This integration should work properly against other Storage Systems, as long as the integration interface (see chapter Configure Universal Task) and functionalities listed in this document fulfil the needs of the Storage System. |
Import Universal Template
...
| Exit Code | Status Classification Code | Status Classification Description | Status Description |
|---|---|---|---|
| 0 | SUCCESS | Successful Execution | SUCCESS: Cloud Data Monitor Task completed successfully. |
| 1 | FAIL | Failed Execution |
|
| 20 | FAIL | Data Validation | DATA VALIDATION ERROR: <informative_message> |
| 22 | FAIL | Failed Execution | FAIL: Cloud File Monitor task executed successfully but updating Credentials failed. |
Extension Output
| Note |
|---|
This Universal Extension produces EXTENSION Output only when the Rclone command fails to be executed. |
Attribute changed is populated as follows:
...
- Python code modifications should not be done.
- Template Modifications
General Section
- "Name", "Extension", "Variable Prefix", "Icon" should not be changed.
Universal Template Details Section
- "Template Type", "Agent Type", "Send Extension Variables", "Always Cancel on Force Finish" should not be changed.
Result Processing Defaults Section
- Success and Failure Exit codes should not be changed.
- Success and Failure Output processing should not be changed.
Fields Restriction Section
The setup of the template does not impose any restrictions, However with respect to "Exit Code Processing Fields" section.- Success/Failure exit codes need to be respected.
- In principle, as STDERR and STDOUT outputs can change in follow-up releases of this integration, they should not be considered as a reliable source for determining success or failure of a task.
- In Event Templates fields "Name", "Time To Live", "Unmapped Attribute Policy", "Attribute Name", "Attribute Type", should not be changed.
Note The suggested configuration for this Universal Extension does not require any updates on Time To Live. However, this field can be tuned for troubleshooting purposes, affecting immediately the time (in minutes) that events are stored in Controller's Event Queue. Configure a low Time To Live value (for example 1 minute), if it is required to review the published Events.
Use Server Operation Inspect Universal Events to view all Universal Events in Controller's event queue.
Users and customers are encouraged to report defects, or feature requests at Stonebranch Support Desk.
...