Re: [PATCH proxmox{,-backup} 0/3] add flag to opt-in using node proxy config for s3 connections

[Robert Obkircher <r.obkircher@proxmox.com>]

nit: commit message 2/3 has a typo "explicitley"

I tested that backups stopped working whenever the checkbox was
enabled while a bogus http proxy was configured.

I also verified that they succeeded when it pointed to tinyproxy on
localhost:8888.


Reviewed-by: Robert Obkircher <r.obkircher@proxmox.com>
Tested-by: Robert Obkircher <r.obkircher@proxmox.com>

On 11.05.26 17:17, Christian Ebner wrote:
> Currently, if set the node proxy config is used unconditionally also
> for S3 client API connections. Since this is however not always the
> intention, allow users to expliciteley opt-in for individual S3
> endpoint configurations.
>
> Reported in the community forum:
> https://forum.proxmox.com/threads/183436/
>
>
> proxmox:
>
> Christian Ebner (1):
>   s3-client: add flag to opt-in for using node proxy for connections
>
>  proxmox-s3-client/src/api_types.rs | 8 ++++++++
>  1 file changed, 8 insertions(+)
>
>
> proxmox-backup:
>
> Christian Ebner (2):
>   api: config: allow editing the use-node-config flag for s3 endpoints
>   ui: add opt-in flag for using the node proxy config for s3 connections
>
>  pbs-datastore/src/datastore.rs | 14 ++++++++++++--
>  src/api2/admin/s3.rs           |  8 +++++++-
>  src/api2/config/s3.rs          | 16 +++++++++++++++-
>  www/window/S3ClientEdit.js     | 13 +++++++++++++
>  4 files changed, 47 insertions(+), 4 deletions(-)
>
>
> Summary over all repositories:
>   5 files changed, 55 insertions(+), 4 deletions(-)
>