Hi,
Le mar. 7 juil. 2020 à 08:23, Jürg Billeter <[email protected]> a écrit :
> bst-artifact-server in BuildStream master still supports the
> ReferenceStorage service used by BuildStream 1.x clients as convenience
> to support 1.x and master clients with the same server.
>
> However, as our goal for 2.x is anyway to replace bst-artifact-server,
> maybe it's now time to drop this. Are there any objections to
> completely removing support for the ReferenceStorage service in bst-
> artifact-server master as part of the move towards the Remote Asset API
> (WIP MR !1978¹)?
I'd like to keep it a little while. As in have 1.94 release with
remote asset (and the junction rework which is also a breaking
change), and remove the reference storage in 1.95.
My idea for resolving this is to support remote asset in buildstream
1.6. Since remote asset can do what the reference storage is currently
doing, it should be fairly straightforward to add support for remote
asset on top of what we have already.
GetReference -> FetchDirectory
key -> uris (using some appropriate URN)
UpdateReference -> PushDirectory
keys -> uris (ditto)
digest -> root_directory_digest
Status is only used to query whether push is supported and can be
easily replaced.
What do you think?
Regards,
Abderrahim
