chore: review

Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
This commit is contained in:
Marco Nenciarini 2025-06-10 11:19:08 +02:00
parent bc70dc8cb3
commit 1b75d6e487
No known key found for this signature in database
GPG Key ID: 589F03F01BA55038
2 changed files with 8 additions and 3 deletions

View File

@ -49,6 +49,7 @@ Uncomment
WAL
WALBackupConfiguration
WALs
amz
api
apiVersion
apiextensions
@ -59,6 +60,7 @@ backend
backends
barmanObjectName
barmancloud
boto
bzip
cd
cloudnative
@ -113,6 +115,7 @@ secretKeyRef
selfsigned
serverName
serviceaccount
sha
sig
storageClass
subcommand

View File

@ -141,9 +141,12 @@ spec:
[...]
```
Due to recent changes to the [boto3](https://github.com/boto/boto3/issues/4392) [Data Integrity Protections for Amazon S3](https://docs.aws.amazon.com/sdkref/latest/guide/feature-dataintegrity.html) implementation, you could hit the [x-amz-content-sha256 Error](https://github.com/cloudnative-pg/plugin-barman-cloud/issues/393).
Due to recent changes in the [boto3 implementation of Data Integrity Protections
for Amazon S3](https://docs.aws.amazon.com/sdkref/latest/guide/feature-dataintegrity.html),
you may encounter the [x-amz-content-sha256 error](https://github.com/cloudnative-pg/plugin-barman-cloud/issues/393).
More details are available in [this related boto3 issue](https://github.com/boto/boto3/issues/4392).
As a workaround set to following environment to the `ObjectStore`.
As a workaround, you can configure the following environment variables in your `ObjectStore` definition:
```yaml
apiVersion: barmancloud.cnpg.io/v1
@ -159,7 +162,6 @@ spec:
[...]
```
Example with DigitalOcean Spaces (SFO3, path-style):
```yaml