Closed sevein closed 6 years ago
@ross-spencer maybe you can take a quick look to this PR? It adds a new experimental transfer_async.py
that we're going to be using @ JiscRDSS so it doesn't really change existing workflows. transfer_async.py
may be evolving as we update the /api/v2beta/package
API.
@sevein Acknowledging I still need to look at this! - One branch relevant to this is, https://github.com/artefactual/automation-tools/commit/76a8b61b5267eed234fd5ce72ff52f3dcf335232 (utils.py is modified) I think we should get this reviewed and merged and then rebase your PR here to fit - what do you think? I'll check with @hakamine if he has any more info on issue #51 but I think this change is independent of that, whatever is causing #51 can be handled in another branch.
I think we should get this reviewed and merged and then rebase your PR here to fit - what do you think?
Sure. Ideally we wouldn't block paying work with minor stuff but I can understand the situation.
Rebased.
On my task list for the end of the day! :+1:
transfer_async.py
is an entry point that reuses what's intransfer.py
but hijacks the only function that needed to be changed (start_transfer
) so the script works against the new/api/v2beta/package
API.transfer_async.py
does not runpre-transfer
scripts because the transfers are started automatically so there is no room for that. In the future,/api/v2beta/package
may learn a newopen
status that may allow us to solve this limitation.This can be considered a walking skeleton. The plan is to eventually have it replace
transfer.py
. The advantage is that/api/v2beta/package
does not block. This was a priority @ JiscRDSS because you can't have a connection open for hours like we do when we're copying big transfers -/api/v2beta/package
solves that problem.I've been testing in my Compose environment and the following command:
Issue: https://jiscdev.atlassian.net/browse/RDSSARK-480. It depends on https://github.com/artefactual/archivematica/pull/936.