Mandatory settings

encryption

See the git-annex encryption documentation.

project

Your project ID from the Google developer console.

Optional settings

bucket

The bucket name, which must be globally unique within GCS. The default name is based on the remote name and UUID.

chunk

Enable chunking.

embedcreds

Set to yes to commit the login credentials to the Git repository so other clones can read them. When using GPG encryption, the default is yes and the credentials are stored encrypted. Otherwise, the default is no; if set to yes, anyone with access to the repo can also access the GCS bucket.

fileprefix

A string, such as mydata/, to be prepended to the name of each object. This allows a bucket to be shared by multiple remotes.

location

The physical location for the data. Can be any of the location strings supported by GCS, such as ASIA, EU, or US. Defaults to US.

public

If yes, newly-uploaded objects are made publicly readable. Defaults to no.

readonly

If set to true when enabling an existing public remote, files can be retrieved without GCS credentials and without gcsannex installed. Requires development version of git-annex.

storageclass

A storage class supported by GCS, such as STANDARD, DURABLE_REDUCED_AVAILABILITY, or NEARLINE. Defaults to STANDARD.

Version 0.2

• Time out stuck requests

• Retry after more types of errors

• Permit encrypted public remotes

• Support showing public URLs in git annex whereis

• Improve compatibility with git-annex < 5.20141219

• Properly accept implicit encryption=hybrid

Version 0.1

• Initial release