In MinIO there are multiple identifiers associated with an upload - name, version ID, ETAG (upon searching, this is a hash, but to a naive user like me it looked like an identifier). Our docs don't make clear which one is the <crate_id> to be used in the API.
The crate_id is related to the name, but not necessarily the exact name - in some cases, like when a .zip file is uploaded, it's more complicated - in the screenshot below the name is workflow-502-4.crate.zip but the API needs you to use crate_id of workflow-502-4.crate to validate it.
We should document more clearly how to determine the crate_id for crates stored in MinIO.
In MinIO there are multiple identifiers associated with an upload - name, version ID, ETAG (upon searching, this is a hash, but to a naive user like me it looked like an identifier). Our docs don't make clear which one is the
<crate_id>to be used in the API.The crate_id is related to the name, but not necessarily the exact name - in some cases, like when a
.zipfile is uploaded, it's more complicated - in the screenshot below the name isworkflow-502-4.crate.zipbut the API needs you to use crate_id ofworkflow-502-4.crateto validate it.We should document more clearly how to determine the crate_id for crates stored in MinIO.