currently, a Move request created via the subscribe API with options request_only=n&move=y will be auto-approved both at source and destination, always deleting the datasets at source.
This may not be optimal for some workflows, where the output needs to be Moved to Tier-1s but kept subscribed at certain Tier-2s for further processing. It could be useful to add a new option to auto-disapprove the Move at source in this case.
Marking as "Need Info" because we should understand how often this is a problem for CompOps, and if they couldn't just use Replica requests in this case instead.
Hi,
currently, a Move request created via the subscribe API with options request_only=n&move=y will be auto-approved both at source and destination, always deleting the datasets at source.
This may not be optimal for some workflows, where the output needs to be Moved to Tier-1s but kept subscribed at certain Tier-2s for further processing. It could be useful to add a new option to auto-disapprove the Move at source in this case.
Marking as "Need Info" because we should understand how often this is a problem for CompOps, and if they couldn't just use Replica requests in this case instead.