LinkinStars commented on issue #97: URL: https://github.com/apache/incubator-answer-plugins/issues/97#issuecomment-2031241650
@calmdev Thanks for the link you gave. I read the documentation in it in detail and found the following. Firstly, the code provided by the official DigitalOcean documentation include the ACL configuration. Therefore, this is a necessary option for DigitalOcean. https://docs.digitalocean.com/reference/api/spaces-api/#hello-world-program <img width="1074" alt="image" src="https://github.com/apache/incubator-answer-plugins/assets/19712692/ebceda97-8bb4-405e-83ca-df8b0df0f140";> Secondly, I found the following description in the documentation. It states that even if the bucket is set to public, any objects uploaded through the s3api will default to private if the ACL is not set. This is the reason behind this issue. https://docs.digitalocean.com/reference/api/spaces-api/#upload-an-object-put <img width="1072" alt="image" src="https://github.com/apache/incubator-answer-plugins/assets/19712692/9998f7d8-90f7-4912-a757-d8e05027e4c1";> In conclusion, **while DigitalOcean is compatible with the S3 API, there are still some differences.** My suggestion is that you can continue using it with your modifications and see if there are any other variations. As for the solutions, we can discuss two options: 1. Use an S3 plugin that provides an environment variable to determine if the user is a DigitalOcean user. If so, add the ACL during the upload process. 2. Develop a separate plugin specifically for DigitalOcean. I can handle this task if needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
