public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: partially-applied: [PATCH proxmox{,-backup} v4 0/8] fix #6716: Add support for http proxy configuration for S3 endpoints
Date: Tue, 31 Mar 2026 23:30:16 +0200	[thread overview]
Message-ID: <177499260903.801440.16178603165380770825.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260327121319.628881-1-c.ebner@proxmox.com>

On Fri, 27 Mar 2026 13:13:11 +0100, Christian Ebner wrote:
> This patch series exposes the nodes proxy config setting to the S3
> clients for datastores backed by an S3 object store.
> 
> To honor crate boundaries, the proxy configuration is refactored to
> be part of pbs-config instead of proxmox-backup. The API types are
> move to pbs-api-types, inlining proxmox_backup::tools::config::from_property_string()
> and NodeConfig::validate() to do so without creating additional unwanted
> dependencies. The schema definition for the proxy is moved to proxmox-http
> instead, already containing the proxy config definition.
> 
> [...]

Applied the proxmox  part, thanks!

[1/2] http: move http proxy schema from PBS to crate's api types
      commit: d3823019f5165917e8076d41dde32d61092e34cf
[2/2] pbs-api-types: move over NodeConfig and related api type from PBS
      commit: 1bcfae925eb426fbaa74b15c2f5c4c07828130e3




      parent reply	other threads:[~2026-03-31 21:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27 12:13 Christian Ebner
2026-03-27 12:13 ` [PATCH proxmox v4 1/8] http: move http proxy schema from PBS to crate's api types Christian Ebner
2026-03-27 12:13 ` [PATCH proxmox v4 2/8] pbs-api-types: move over NodeConfig and related api type from PBS Christian Ebner
2026-03-31 11:17   ` Hannes Laimer
2026-03-27 12:13 ` [PATCH proxmox-backup v4 3/8] pbs-config: use http proxy schema moved to proxmox-http crate Christian Ebner
2026-03-27 12:13 ` [PATCH proxmox-backup v4 4/8] config: inline NodeConfig::validate() to its only call side Christian Ebner
2026-03-27 12:13 ` [PATCH proxmox-backup v4 5/8] config: use moved NodeConfig definitions in pbs-api-types Christian Ebner
2026-03-27 12:13 ` [PATCH proxmox-backup v4 6/8] tools: drop unused from_property_string() helper Christian Ebner
2026-03-27 12:13 ` [PATCH proxmox-backup v4 7/8] config: move node config into pbs-config, including helper tools Christian Ebner
2026-03-27 12:13 ` [PATCH proxmox-backup v4 8/8] fix #6716: pass node http proxy config to s3 backend Christian Ebner
2026-03-31 11:18 ` [PATCH proxmox{,-backup} v4 0/8] fix #6716: Add support for http proxy configuration for S3 endpoints Hannes Laimer
2026-03-31 21:30 ` Thomas Lamprecht [this message]

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=177499260903.801440.16178603165380770825.b4-ty@proxmox.com \
    --to=t.lamprecht@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal