Ben McClelland 6f77cec3bd fix: s3 backend requires nil values for input params ...

For any uninitialized input values, the s3 sdk expects these to
be set to nil instead of the type zero value. Setting to the zero
value is incorrectly making the server request think we are
trying to set those parameters.

This sets all input parameters to nil for the default values. Many
of these are already nil from the frontend, but this should
protect against a future addition of input params for an api
requests and not remembering to add teh zero value check on in
the s3 backend.

We were previously getting the following error for put-object:
<Error><Code>InvalidArgument</Code><Message>x-amz-object-lock-retain-until-date and x-amz-object-lock-mode must both be supplied</Message><Resource></Resource><RequestId></RequestId><HostId></HostId></Error>

2025-02-28 13:31:24 -08:00

..

client.go

fix: remove deprecated WithEndpointResolver s3 client option

2024-06-04 11:09:29 -07:00

s3.go

fix: s3 backend requires nil values for input params

2025-02-28 13:31:24 -08:00