Issue with object storage when sse-s3 is not supported. Can we make this optional (is sse-c an option?)

[chris-milsted]

The two encryption options (AES or aws:kms) call sse-s3. This is not supported on linode object at the moment, so I would like to be able to specify encryption: "" in the wal archive. When I try this I get

$ k create -f barmanObjectStore.yaml The ObjectStore "paris-object" is invalid: spec.configuration.wal.encryption: Unsupported value: "": supported values: "AES256", "aws:kms"

Can we make this optional or allow a key to be specified so that we can use sse-c instead?

[martinmarques]

@chris-milsted please check this reply from @alwinzwets
#957 (comment)

[chris-milsted]

That reply almost works.... as I mentioned I did try to pass in encryption: "" but it fails as below:

$ k create -f barmanObjectStore.yaml The ObjectStore "paris-object" is invalid: spec.configuration.wal.encryption: Unsupported value: "": supported values: "AES256", "aws:kms"

Is this a cloud native pg issue or a barman issue on this validation?