Inconsistency between Azure Blob Storage and other storage types about athens HOT 4 OPEN

@Eitan03 one could argue that the internal representation of the storage is not of concern to the user, so I wonder what exactly your use case is. Transferring storage is not in focus of Athens I would say and when it's needed, it is a one-time task that can be easily covered with custom scripting. Or am I wrong?

However, does this issue prevent pre-filling with pacmod? Or how do you "fill" the storage?
In other words: what prevents you from "filling" the new storage from scratch?

from athens.

linking issues #1583

from athens.

for documentation purposes (when we discuss this), here is a rough overview of code parts:

• Azure: Uses common upload code
• S3: Uses common upload code
• GCP: uses the same as Azure but not the common code
• Mongo: Does it own thing, and thats ok
• Minio: Uses module/version style
• FS: Uses module/version style

so currently, if I'm not mistaken, pacmod works with MinIO and filesystem storage options, not with Cloud provider storage. For an offline mode (some older discussions here: #1538) one should be able to use one of these two.

The argument to leave it as is would be that the internal storage representation of a cloud storage should not be of concern to the user and it could change with future releases. Also, a different storage provider may require a different representation.

from athens.

We should look at this inconsistency and find a reason for it (and document it) or correct it for version 1.0.0

from athens.