Allow zarr to be reingested even if was already ingested?

[yarikoptic]

Echoing #1138 (comment) discussion suggesting that client might still want/need to trigger /ingest process and in particular having in mind that we cannot revoke upload presigned URLs (#1162) and thus some "lost" client can still upload some outdated file etc, we might need a way to "force" re-ingestion of the zarr archive. But that should not be allowed "blindly" and for everyone since open DoS attack (keep service busy reingesting) so may be more thinking is needed. May be should be left at the level of a service script. WDYT?

[waxlamp]

A service script or an admin-only action endpoint.

[waxlamp]

@AlmightyYakob, I think this may be closeable now--can you please assess?

[jjnesbitt]

This would still apply, but is now the finalize endpoint. We could gate that with a force flag, allowed by admins only.

[waxlamp]

I think either a button in the admin console, or even just a service script, would be the right interface to it. What do you think?

[jjnesbitt]

I think either a button in the admin console, or even just a service script, would be the right interface to it. What do you think?

I think that makes sense, since as a normal user, you can't update a zarr out of band, which is the only way you'd need to run this anyway. We do already have the option in the admin console, but it doesn't use the force=True flag, making it largely useless. I'll make a PR to fix that.

[dandibot]

🚀 Issue was released in v0.3.27 🚀