You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the trust serializer expects an io.ReadCloser from zip.OpenReader when passed to serializer.Read() - this works when the zip file is being opened from a path on disk, but doesn't allow in-memory decompression of zip files, which may be required when using secrets storage such as Google Secret Manager or Vault. Although in most cases the secret will be mounted to a pod and read as though it were on disk, it would still be useful to have this utility.
in serializer.Read in ZIP mode perform a type check to see if the reader is a zip.ReadCloser, a zip.Reader, or not.
If zip.ReadCloser - continue as normal; if not a zip.Reader, create a zip.Reader from the reader.
Process the zip.Reader independently of the zip.ReadCloser Using advice from this stackoverflow post
Right now the trust serializer expects an
io.ReadCloser
fromzip.OpenReader
when passed toserializer.Read()
- this works when the zip file is being opened from a path on disk, but doesn't allow in-memory decompression of zip files, which may be required when using secrets storage such as Google Secret Manager or Vault. Although in most cases the secret will be mounted to a pod and read as though it were on disk, it would still be useful to have this utility.serializer.Read
in ZIP mode perform a type check to see if the reader is azip.ReadCloser
, azip.Reader
, or not.zip.ReadCloser
- continue as normal; if not azip.Reader
, create azip.Reader
from the reader.zip.Reader
independently of thezip.ReadCloser
Using advice from this stackoverflow postSee also this small test issue in the
directory
repo.The text was updated successfully, but these errors were encountered: