From: Gabriel Goller <g.goller@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>
Cc: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [PATCH proxmox-backup] api: return s3 client errors during datastore create with context
Date: Thu, 24 Jul 2025 16:36:23 +0200 [thread overview]
Message-ID: <uenyttvhketbrkxvdvgqe6355eenit53v5yizfljgvddircugp@5awmnak3a7r5> (raw)
In-Reply-To: <20250724124236.838266-1-c.ebner@proxmox.com>
Consider:
Tested-by: Gabriel Goller <g.goller@proxmox.com>
We could do this nicer by just always returning the full error from the
api from all endpoints, but for that we'd have to check thoroughly to
avoid showing sensitive data.
In the meantime this is perfect!
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-07-24 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 12:42 Christian Ebner
2025-07-24 14:36 ` Gabriel Goller [this message]
2025-08-05 13:12 ` [pbs-devel] applied: " Thomas Lamprecht
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=uenyttvhketbrkxvdvgqe6355eenit53v5yizfljgvddircugp@5awmnak3a7r5 \
--to=g.goller@proxmox.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox