all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH proxmox v2 2/4] s3-client: return dedicated error type for delete object response
Date: Wed,  4 Mar 2026 14:59:18 +0100	[thread overview]
Message-ID: <20260304135922.717714-3-c.ebner@proxmox.com> (raw)
In-Reply-To: <20260304135922.717714-1-c.ebner@proxmox.com>

In order to be able to reuse the delete object API calls as opt-in
replacement for delete objects API calls, but not suppress the
HTTP status code on failure.

Use an enum to distinguish the two cases and implement the Into trait
on it to be albe to easily convert back to an anyhow::Error type.

Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
changes since version 1:
- not present in previous version

 proxmox-s3-client/src/client.rs          |  5 ++-
 proxmox-s3-client/src/response_reader.rs | 39 +++++++++++++++++++++---
 2 files changed, 38 insertions(+), 6 deletions(-)

diff --git a/proxmox-s3-client/src/client.rs b/proxmox-s3-client/src/client.rs
index 3d0af5d6..e536614b 100644
--- a/proxmox-s3-client/src/client.rs
+++ b/proxmox-s3-client/src/client.rs
@@ -554,7 +554,10 @@ impl S3Client {
 
         let response = self.send(request, None).await?;
         let response_reader = ResponseReader::new(response);
-        response_reader.delete_object_response(object_key).await
+        response_reader
+            .delete_object_response(object_key)
+            .await
+            .map_err(Into::into)
     }
 
     /// Delete multiple objects from a bucket using a single HTTP request.
diff --git a/proxmox-s3-client/src/response_reader.rs b/proxmox-s3-client/src/response_reader.rs
index be7c0950..3478ea7c 100644
--- a/proxmox-s3-client/src/response_reader.rs
+++ b/proxmox-s3-client/src/response_reader.rs
@@ -1,6 +1,6 @@
 use std::str::FromStr;
 
-use anyhow::{anyhow, bail, Context, Error};
+use anyhow::{anyhow, bail, format_err, Context, Error};
 use http_body_util::BodyExt;
 use hyper::body::{Bytes, Incoming};
 use hyper::header::HeaderName;
@@ -226,6 +226,26 @@ pub struct Bucket {
     pub creation_date: LastModifiedTimestamp,
 }
 
+pub(crate) enum DeleteError {
+    Response(DeleteObjectError),
+    Parsing(Error),
+}
+
+impl Into<Error> for DeleteError {
+    fn into(self) -> Error {
+        match self {
+            Self::Response(delete_error) => {
+                if let Some(code) = delete_error.code {
+                    format_err!("unexpected status code: {code}")
+                } else {
+                    format_err!("failed to generate error, missing error status code")
+                }
+            }
+            Self::Parsing(error) => error,
+        }
+    }
+}
+
 impl ResponseReader {
     /// Create a new response reader to parse given response.
     pub(crate) fn new(response: Response<Incoming>) -> Self {
@@ -364,22 +384,31 @@ impl ResponseReader {
     pub(crate) async fn delete_object_response(
         self,
         key: S3ObjectKey,
-    ) -> Result<DeletedObject, Error> {
+    ) -> Result<DeletedObject, DeleteError> {
         let (parts, _body) = self.response.into_parts();
 
         match parts.status {
             StatusCode::NO_CONTENT => (),
-            status_code => bail!("unexpected status code {status_code}"),
+            status_code => {
+                return Err(DeleteError::Response(DeleteObjectError {
+                    code: Some(status_code.to_string()),
+                    key: Some(key),
+                    message: None,
+                    version_id: None,
+                }));
+            }
         };
 
         let delete_marker = Self::parse_optional_header(
             HeaderName::from_static("x-amz-delete-marker"),
             &parts.headers,
-        )?;
+        )
+        .map_err(|err| DeleteError::Parsing(err))?;
         let delete_marker_version_id = Self::parse_optional_header(
             HeaderName::from_static("x-amz-version-id"),
             &parts.headers,
-        )?;
+        )
+        .map_err(|err| DeleteError::Parsing(err))?;
 
         Ok(DeletedObject {
             delete_marker,
-- 
2.47.3





  parent reply	other threads:[~2026-03-04 13:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 13:59 [PATCH proxmox{,-backup} v2 0/6] fix #7078: Add quirk for providers not supporting deleteObjects Christian Ebner
2026-03-04 13:59 ` [PATCH proxmox v2 1/4] s3-client: parse and return headers for delete object response Christian Ebner
2026-03-04 13:59 ` Christian Ebner [this message]
2026-03-04 13:59 ` [PATCH proxmox v2 3/4] s3-client: extend provider quirks by delete objects via delete object Christian Ebner
2026-03-04 13:59 ` [PATCH proxmox v2 4/4] s3-client: return list of errors when deleting by prefix Christian Ebner
2026-03-04 13:59 ` [PATCH proxmox-backup v2 1/2] datastore: s3: modify delete objects api and log exposed errors Christian Ebner
2026-03-04 13:59 ` [PATCH proxmox-backup v2 2/2] fix #7078: ui: exponse DeleteObjects via DeleteObject provider quirk Christian Ebner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260304135922.717714-3-c.ebner@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal