As well as --forbid-special and --allow-restricted, another option in this group could be added: --tarball, which takes the input files from iRODS and uploads them to S3 as a tarball. In which case, the target S3 location must have a key (which doesn't exist, unless --force is specified).
(n.b., This may be tricky to reconcile with #2.)
(n.b., --tarball would imply --ignore-avus as it wouldn't make sense to apply data object AVUs to a tarball of them.)
As well as
--forbid-specialand--allow-restricted, another option in this group could be added:--tarball, which takes the input files from iRODS and uploads them to S3 as a tarball. In which case, the target S3 location must have a key (which doesn't exist, unless--forceis specified).(n.b., This may be tricky to reconcile with #2.)
(n.b.,
--tarballwould imply--ignore-avusas it wouldn't make sense to apply data object AVUs to a tarball of them.)