Instead of utilising a package in order to handle different types of cloud provider I have created a provider agnostic interface which integrates in the colossus logic
I believe this will allow us to easily add support for other providers in the future, by using their official sdk.
This also was useful in order to keep the changes to existing colossus logic to a minimal level (as the logic is already complex by itself).
The files localCache has been enhanced in order to keep track of which files are on the bucket and which files are on the local volume.
Only "accepted" data objects are stored on the bucket
The implementation is the same as suggested here:
4981 (last comment by Mokhtar)
Instead of utilising a package in order to handle different types of cloud provider I have created a provider agnostic interface which integrates in the colossus logic
I believe this will allow us to easily add support for other providers in the future, by using their official sdk. This also was useful in order to keep the changes to existing colossus logic to a minimal level (as the logic is already complex by itself).
The files
localCachehas been enhanced in order to keep track of which files are on the bucket and which files are on the local volume. Only "accepted" data objects are stored on the bucket