From 614d438217376d0e1403eca66b52cb4659c72b18 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Wed, 31 Jan 2024 20:40:44 +0000 Subject: [PATCH] question about migrating URLs between remotes --- .../how_to___34__move__34___URL_between_remotes__63__.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 doc/forum/how_to___34__move__34___URL_between_remotes__63__.mdwn diff --git a/doc/forum/how_to___34__move__34___URL_between_remotes__63__.mdwn b/doc/forum/how_to___34__move__34___URL_between_remotes__63__.mdwn new file mode 100644 index 0000000000..bdf73143da --- /dev/null +++ b/doc/forum/how_to___34__move__34___URL_between_remotes__63__.mdwn @@ -0,0 +1,6 @@ +In [backups2datalad](https://github.com/dandi/backups2datalad/pull/21) we are implementing support for "embargoed" data -- files which would require authorization initially. To provide authentication support we enable/configure `git-annex-remote-datalad` to handle them. But in the future, when data gets unembargoed we would need to remove/disable `datalad` special remote and migrate (the same) URLs to no longer be associated with it and rather be handled by `web` remote. Generally the use case might desire moving URLs between remotes (e.g. from `datalad` to `datalad-next`), or migrating from `web` into an external remote. + +Is it already possible reasonably well, or would require messing with `.web` files in the git-annex branch? + +[[!meta author=yoh]] +[[!tag projects/dandi]]