fix: the versioning/object lock documentation appropriately (#9988)

- Move the bucket level features into `docs/bucket` directory
- fix issue template and simplify some of them
This commit is contained in:
Harshavardhana
2020-07-08 08:44:43 -07:00
committed by GitHub
parent fa211f6a10
commit 60417950c7
11 changed files with 141 additions and 130 deletions

View File

@@ -35,3 +35,4 @@ To permanently delete an object you need to specify the version you want to dele
- Versioning state applies to all of the objects in the versioning enabled bucket. The first time you enable a bucket for versioning, objects in the bucket are thereafter always versioned and given a unique version ID.
- Existing or newer buckets can be created with versioning enabled and eventually can be suspended as well. Existing versions of objects stay as is and can still be accessed using the version ID.
- All versions, including delete-markers should be deleted before deleting a bucket.
- **Versioning feature is only available in erasure coded and distributed erasure coded setups**.