You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried passing --transfer-info=@json:'{"ascp_args":["--no-write"]}' but this doesn't seem to have any effect, perhaps the ascp_args are only relevant when ascli is calling ascp locally?
The text was updated successfully, but these errors were encountered:
options passed on --transfer-info are specific to the agent specified in --transfer.
and yes, ascp_args is only valid for the direct (default) agent, which spawns directly ascp, and so has the capabilitity to add this special argument.
When using the node agent, the only available transfer parameters (eventually used to start ascp, and so the transfer), are the ones in the node api: POST /ops/transfers
Hi Team,
Is there a way to specify a no write option when orchestrating transfers between 2 storage nodes?
We're currently initiating transfers as follows:
Where
transfer_spec.json
contains like:I've tried passing
--transfer-info=@json:'{"ascp_args":["--no-write"]}'
but this doesn't seem to have any effect, perhaps theascp_args
are only relevant whenascli
is callingascp
locally?The text was updated successfully, but these errors were encountered: