/cc @frankyn Follow-on from PR #7460.
Currently, the GCS back-end has a bug for signed URLs using customer-supplied encryption key headers (x-goog-encryption-key and x-goog-encryption-key-sha256). Once a fix for that bug is rolled out, add system tests which show using the CSEK headers to build V4 signed upload / download URLs, and exercise them.
/cc @frankyn Follow-on from PR #7460.
Currently, the GCS back-end has a bug for signed URLs using customer-supplied encryption key headers (
x-goog-encryption-keyandx-goog-encryption-key-sha256). Once a fix for that bug is rolled out, add system tests which show using the CSEK headers to build V4 signed upload / download URLs, and exercise them.