Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
fts-rest 3.9.3
-
Security Level: Public Data (This ticket is visible to anyone on the internet and will be indexed by search engines)
-
None
Description
Given a bulk submission file, fts-rest-transfer-submit only parses the files field. This issue proposes that the client also parse a parameters field.
Example
Given the following bulk submission file:
{
"files": [
{
"sources": ["http://example-01.cern.ch:8443/example/hello.txt"],
"destinations": ["http:/example-02.cern.ch:8443/example/hello.txt"]
}
],
"params" : {
"s3alternate" : true,
"ipv4" : true,
"nostreams" : 4
}
}
Upon running the client, the parameters are not taken into account:
> fts-rest-transfer-submit --dry-run -s https://fts3-devel.cern.ch:8446 -f submission.json
{
"files": [
{
"sources": [
"http://example-01.cern.ch:8443/example/hello.txt"
],
"metadata": "None",
"checksum": "ADLER32",
"filesize": null,
"destinations": [
"http:/example-02.cern.ch:8443/example/hello.txt"
]
}
],
"params": {
"credential": null,
"timeout": null,
"fail_nearline": false,
"gridftp": null,
"ipv6": false,
"bring_online": null,
"multihop": false,
"s3alternate": false,
"nostreams": null,
"overwrite": false,
"reuse": false,
"retry": 0,
"spacetoken": null,
"copy_pin_lifetime": -1,
"job_metadata": "None",
"verify_checksum": "none",
"source_spacetoken": null,
"ipv4": false
}
}
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- mentioned on
