mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

proxied exporttree=yes versionedexport=yes remotes are not untrusted

Browse source 
This removes versionedExport, which was only used by the S3 special
remote. Instead, versionedexport=yes is a common way for remotes to
indicate that they are versioned.
This commit is contained in:
Joey Hess 2024-08-08 15:13:12 -04:00
parent 5c36177e58
commit 3ea835c7e8
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
16 changed files with 23 additions and 53 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/todo/git-annex_proxies.mdwn
View file

@ -33,22 +33,6 @@ Planned schedule of work:
* Working on `exportreeplus` branch which is groundwork for proxying to
exporttree=yes special remotes. Need to merge it to master.
* Versioned exports are not untrustworthy. But checking that for a proxied
remote would need to construct a Remote using the special remote's config.
For eg S3 (the only versioned one currently), that would need the S3
creds to be set in the environment.
For an external special remote that uses the (currently draft) extension,
the program would need to be installed to check how it responds to
VERSIONED.
Constructing a special remote in order to use it proxied does not seem
feasible.
versionedExport could be changed be a pure function from
ParsedRemoteConfig. But that would not help with external special remotes.
## completed items for August
* Special remotes configured with exporttree=yes annexobjects=yes