Just to confirm, the goal here is to be able to set a key when uploading a file. Eventually we might want a key-derivation library involved, but for now this is just about setting a key on a per-file basis.

Let me know how far off #1364 (comment) is from what you're looking for.

If we only support uploading a file, the user would be blocked out from other operations, like downloading it. The way this PR works is:

• the user provides a passphrase to file.encrypt()
• every API request made with a file object (file.download, .copy, .createWriteStream, etc) will pass the generated key so that these operations don't fail

@callmehiphop PTAL!

@stephenplusplus I think npm might have messed up your most recent release of gcs-resumable-upload, both travis and my local are failing to install v0.7.x, however v0.6.x still seems to be installing fine in master.

Fixed... v0.7.1.

This might be a slightly off-topic question, but the upstream documentation for sending encryption keys also mentions a separate set of headers for rewrite operations, which we don't appear to support - any reason why that is?

rewrite is new! At least, since we had a Storage deep dive. Mind making an issue to remind us to add support?

Done! #1373

Changes Unknown when pulling 6e1df56 on stephenplusplus:spp--1361 into * on GoogleCloudPlatform:master*.