<@U01867G8AA0> what’s the status on the “Return a ...
# help
@Ariel Shaqed (Scolnicov) what’s the status on the “Return a
-like object on file up-/downloads containing basic version info” plan re: the lakeFS server? I saw that the RFC was merged, and that you commented on the idea. Basically for now, I can emulate this in the frontend by grabbing the object info as normal (via
), and then basically doing the equivalent of
git rev-parse $ref
with the requested revision. The
is object staged or committed
use case you asked for is e.g. integrity checking: Am I working with properly tracked/committed data, or a “dirty” untracked version staged on main by my colleague without my knowledge? This would matter more when pulling data using raw branch names instead of commit SHAs, but from my experience, that’s quite common actually.
fwiw: I can hack up a descriptive GH issue no problem, just wanted to get a feeling for if this is even interesting from a maintainer’s perspective.
AFAIK we actually have the data in hand: on upload we literally just wrote it to staging, in download we had it. Also I'm pretty sure we already give it on upload, and also on download via the s3 gateway. So no promises but it looks like a useful bit of functionality. Thanks!
The main issue might be how to describe it for download in OpenAPI. I say we should go for it.