I am currently evaluating unFTP for sharing data in Azure Blob Storage over FTP(S). I noticed that with an azblob storage backend (SBE) it is not possible to cd in a given blob prefix. When using a filesystem SBE this work as expected. I am aware that azblob storage is basically a flat list of files. But I was kind of expecting that unFTP would abstract over this somehow.
Is this intented behaviour? Or a consequence of using Opendal as library to interface with azblob? I could not find anything in the unFTP docs about azblob SBE (but also noticed it has been added quite recently).
See behaviour of unFTP with filesystem SBE:
Behaviour with azblob SBE:
I made a small docker-compose deployment example with Azurite to test the behaviour.
I am currently evaluating unFTP for sharing data in Azure Blob Storage over FTP(S). I noticed that with an azblob storage backend (SBE) it is not possible to cd in a given blob prefix. When using a filesystem SBE this work as expected. I am aware that azblob storage is basically a flat list of files. But I was kind of expecting that unFTP would abstract over this somehow.
Is this intented behaviour? Or a consequence of using Opendal as library to interface with azblob? I could not find anything in the unFTP docs about azblob SBE (but also noticed it has been added quite recently).
See behaviour of unFTP with filesystem SBE:
Behaviour with azblob SBE:
I made a small docker-compose deployment example with Azurite to test the behaviour.