-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] S3 Bucket support as alternative to local path #53
Comments
Should be feasible. A web service provides plugin meta infomation, storage service (like S3) provides plugin jar repository, and download/update to local to be loaded by pluginManager. Do you interest to build this "plugin service". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello
we extended the local path I/O structure with volume concept in docker-compose and it worked perfectly but now we need to swich to a "bucket" concept instead of "volume" concept.
Have you got any idea about how it could be possible to use the external Amazon AWS S3 SDK to interact with buckets instead of just with local path?
Thank you in advance for any suggestion about it. We have knowledge about AWS S3 SDK if it can help.
The text was updated successfully, but these errors were encountered: