fix: allow string encryption keys #1418
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
** edit ** I don't know if this was the right thing to do. Holding off for now.
The
encryptionKey
ofbucket.upload({encryptionKey})
,bucket.file('name', {encryptionKey})
, and possibly others were said to accept either a String or Buffer. However, if a base64 string was provided, it was being re-encoded. This change will allow both to be handled separately, passing along the correct base64-encoded encryption key to the API.