From 3a47f7d22f954e7e3548ef3cb8e96320769f0ef9 Mon Sep 17 00:00:00 2001
From: Milan <milan.danecek@gmail.com>
Date: Fri, 25 Aug 2023 00:20:09 +0200
Subject: [PATCH] s3 versioning fix code
---
object-storage/s3-features.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/object-storage/s3-features.md b/object-storage/s3-features.md
index a278117..7e44636 100644
--- a/object-storage/s3-features.md
+++ b/object-storage/s3-features.md
@@ -99,7 +99,7 @@ Now we will put new object into created bucket.
"VersionId": "KdS5Yl0d06bBSYriIddtVb0h5gofiNX"
}
-Now we can change the file updating the body.
+Now we can change the file via updating the body.
aws s3api put-object --key "file name" --body "file path 2" --bucket "bucket name" --profile "profil name" --endpoint-url=https://s3.cl2.du.cesnet.cz
@@ -245,6 +245,7 @@ Now we can list the particular versions.
For a versionless bucket, the object is permanently deleted and cannot be recovered. For a versioned bucket, all versions remain in the bucket and RGW inserts a delete flag that becomes the current version:
aws s3api list-object-versions --bucket "bucket name" --profile "profil name" --endpoint-url=https://s3.cl2.du.cesnet.cz
+
{
"Versions": [
{
@@ -306,6 +307,7 @@ In the case of a versioned bucket, if an object with a specific VersionID is del
Now we can check the object versions again.
aws s3api list-object-versions --bucket "bucket name" --profile "profil name" --endpoint-url=https://s3.cl2.du.cesnet.cz
+
{
"DeleteMarkers": [
{
--
GitLab