applied: [PATCH proxmox{,-backup} v4 0/8] fix #6716: Add support for http proxy configuration for S3 endpoints

[Thomas Lamprecht <t.lamprecht@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, with the trivial context merge conflict from the S3 counter series
resolved, thanks!

btw. I fixed up the s/call side/call site/ typo that was present in three
commit messages.

[1/6] pbs-config: use http proxy schema moved to proxmox-http crate
      commit: 9759277cc6cd6d0c8fc28aecced4f6ccdefe34d9
[2/6] config: inline NodeConfig::validate() to its only call side
      commit: 28f6a7134d9eb2bec8495407aa7d69f8d194c2f6
[3/6] config: use moved NodeConfig definitions in pbs-api-types
      commit: 6279216832c6c3a520e656f3641d141b247c5561
[4/6] tools: drop unused from_property_string() helper
      commit: ff149a6a3faf78e61d057e9dcaa3f3d5966cbae7
[5/6] config: move node config into pbs-config, including helper tools
      commit: 6a6bd6143dfe7014ab5dc2dc3aae4bee32098df6
[6/6] fix #6716: pass node http proxy config to s3 backend
      commit: fbf8d1b250113e8c754aeae807fe3c78a95c3101