Support for extension type or name mapping conventions in ObjectStore #204
Description
Describe the solution you'd like
Accessing the ObjectStore with a native client, i will only see guids without extensions,
that does not allow to open the file with the correct app for missing extension type.
In general, it would be great to be able to control the generated file naming more flexible.
In our solutions, we have splittet the admin part (CAP Attachment) from the delivering,
because we do not use a database to store information.
We just want to use the plugin to upload attachments to a product and
use the same structure in the bucket, like
/BUCKET/MY_PRODUCT_ID_1/FILE_1.webp
/BUCKET/MY_PRODUCT_ID_2/FILE_2.jpeg
Beeing able to create folders for a set of files.
Using it this way, the access layer is able to return a json info on all files for a given
product_id and then use this info to stream files.
The benefit is, that we can manage files for a remote services (eg SAP Product API)
without the need to store everything in a DB.
Also allowing to control naming (like escaped real file names) makes it easier
to avoid duplicated files, because currently you can upload the same file as often as you want.
A switch to select if you want to map files in database or live from content would be
great in conjunction with pattern based filename support.
Describe alternatives you've considered
We are still using our own implementation, but from a midtime perspective i would like
to switch over to this plugin (especially if you start to support also Azure).
Additional context
If you would allow to use attachment functionality for external services,
storing objects on a choosen semantic key
and maybe retrieving relevant object keys like we do using
https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html
using the ObjectID escaped as a folder prefix to performantly beeing able to retrieve relevant keys
would be a great enhancement.
Customer Info
Company: UNIORG Group
Regards Holger