The topic of S3 path style access is being discussed. recursivecodes requested the feature be added back into the core, as it is required for Oracle Cloud Object Storage. However, Falco explained that the feature was removed to maintain compatibility with AWS S3, Google Cloud Storage, and Digital Ocean Spaces, and that Oracle Cloud compatibility alone is not enough to justify the added complexity. Falco also suggested that Oracle may fix the issue in their roadmap, and that a custom plugin could be an alternative solution. recursivecodes acknowledged this and will investigate further.
I see that there was support for using “path style” access for S3 at one point, but it was removed. Can we figure out a compromise to get this added back in as well as support for chunked encoding? Some cloud providers S3 compatible endpoints require just a tiny bit more configuration and these two settings in particular are required to use Oracle Cloud Object Storage:
So we have compatibility with AWS S3, Google Cloud Storage, Digital Ocean Spaces. I’m afraid compatibility with Oracle Cloud won’t be enough to justify the added complexity in core.
Doesn’t Oracle plans on fixing this in their roadmap? If not, the only road would be adding the path style support in a custom plugin.