Rework the S3 compatibility page #108

Closed
opened 2021-09-17 13:38:00 +00:00 by quentin · 3 comments
Owner

I think we shoud:

  • update it
  • use a table
  • have a description to explain when a feature is partially implemented
  • linked to the corresponding issue when a feature is planned

We could take some inspiration from other projects:

I think we shoud: - update it - use a table - have a description to explain when a feature is partially implemented - linked to the corresponding issue when a feature is planned We could take some inspiration from other projects: - https://github.com/exoscale/pithos/blob/master/doc/source/api.rst - https://docs.riak.com/riak/cs/2.1.1/references/apis/storage/s3.1.html
quentin added the
Documentation
label 2021-09-17 13:38:00 +00:00
quentin self-assigned this 2021-09-17 13:38:01 +00:00

is this covered by the compatibility target and compatibility status pages?

is this covered by the [compatibility target](https://garagehq.deuxfleurs.fr/working_documents/compatibility_target.html) and [compatibility status](https://garagehq.deuxfleurs.fr/reference_manual/s3_compatibility.html) pages?
Owner

It's pretty good yeah, but as Quentin said we should probably add links to issues in the bug tracker for caveats and endpoints not yet implemented

It's pretty good yeah, but as Quentin said we should probably add links to issues in the bug tracker for caveats and endpoints not yet implemented
Owner

Also, the page is out of date as we now have vhost style buckets :)

Also, the page is out of date as we now have vhost style buckets :)
lx closed this issue 2022-01-10 13:15:28 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#108
No description provided.