IBM / aspera-cli

IBM Aspera CLI

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Aspera CLI Directory ownership issue

mukeshrsharma opened this issue · comments

Hi Team
After Transfer data from Aspera CLI tool the ownerahip of Directory are getting changed, So whatever Ownership is there on the Source directory we want to keep the same ownership at destination, we are using below command to tranfer data, please assist
/usr/local/.aspera/cli/bin/aspera shares download -i -H=sgscvau50097.in623.corpintra.net --username AGSC_RDI_s_transfe -s=/source_path -d=/Destination_path

Hi,

The command line aspera (version 3) is deprecated.

This github is about version 4 only.

So, first user version 4. (the version of this github)

Concerning "Shares", it is usually not supposed to keep the ownership of original files (on server side).

Of course, preserving ownership assumes that the same user exists on both source and destination.

Still, ascp supports many options, among those, there is preservation of ownership and ascli supports all options of ascp, typically throiugh the user of "transfer specification" .

ascli can list transfer spec parameters with: ascli conf ascp spec
Those are also listed in Aspera API documentation, e.g. :
https://developer.ibm.com/apis/catalog/aspera--aspera-transfer-sdk/API%20Reference

For example, you'll find parameter: preserve_file_owner_uid

So, an example of command would be:

ascli shares repository download /source_path --to-folder=/dest_path --url=https://shares.example.com --username=_username_here_ --password=_pass_here_ --ts=@json:'{"target_rate_kbps":100000,"preserve_file_owner_uid":true}'

Any options can be placed in a config file, refer to doc.