Why is this an issue?
When listing object versions with cloud storage versions test-bucket myfile, the VERSION ID column shows null even though the object was just uploaded. This makes the command output useless for identifying specific versions.
What is causing it?
The API likely returns null or empty string for the version ID, which is then displayed as-is. Many object storage systems use null version IDs for non-versioned objects.
How can it be solved?
Either:
- Filter out null version IDs from the output, or
- Show a placeholder like "(null)" or "-" for unversioned objects, or
- Hide the VERSION ID column when all entries have null values
Category
Severity
Steps to reproduce
cloud storage upload test-bucket /etc/hostname --key myfile
cloud storage versions test-bucket myfile
# Output:
# VERSION ID | LATEST | SIZE | CREATED AT
# null | true | 14 | 2026-05-07T16:52:02+03:00
Why is this an issue?
When listing object versions with
cloud storage versions test-bucket myfile, the VERSION ID column showsnulleven though the object was just uploaded. This makes the command output useless for identifying specific versions.What is causing it?
The API likely returns
nullor empty string for the version ID, which is then displayed as-is. Many object storage systems use null version IDs for non-versioned objects.How can it be solved?
Either:
Category
Severity
Steps to reproduce