If you've ever had to handle a large volume of data, chances are that you've had to interact with boto3 / azure.storage.blob.

Did you love the experience? We didn't totally either. We needed some high-level functions that could be relied on to work 98% of the time, and that allowed us to be agnostic in terms of which cloud provider/object storage protocol we're working on.

ecodev-cloud (and it's associated documentation) does just that, with some (relatively... 😊) cloud-agnostic load/save/search/copy/move methods.

By setting some env variables and adding ecodev-cloud to your usual requirements, it should be easier to interact with cloud storages (this was the case for us, and we surely hope that it will be the case for you too!).

In any case, do not hesitate to take what you need, read the code, learn from what we did (and share your own insights, we would be delighted )...

The local dev setup relying on minio and/or azurite might prove useful to you as well (we found very few relevant information on azurite).

Special thanks to Olivier Gabriel , Amaury Salles , Yoann Diep , Dorian KODELJA and Japheth Yates for the support!

Happy coding from the EcoAct CDA Python team! 😊