Note: Examples require CLI v2.

A release blobstore contains release blob and created final releases.

Access to release blobstore is configured via two files:

  • config/final.yml (checked into Git repository): contains blobstore location
  • config/private.yml (is NOT checked into Git repository): contains blobstore credentials

CLI supports two different blobstore providers: s3 and local.

S3 Configuration

S3 provider is used for most production releases. It’s can be used with any S3-compatible blobstore (in compatibility mode) like Google Cloud Storage and Swift.

config/final.yml:

---
blobstore:
  provider: s3
  options:
    bucket_name: <bucket_name>

config/private.yml:

---
blobstore:
  options:
    access_key_id: <access_key_id>
    secret_access_key: <secret_access_key>

See Configuring S3 release blobstore for details and S3 CLI Usage for additional configuration options.


Local Configuration

Local provider is useful for testing.

config/final.yml:

---
blobstore:
  provider: local
  options:
    blobstore_path: /tmp/test-blobs

Nothing in config/private.yml.


Migrating blobs

CLI does not currently provide a builtin way to migrate blobs to a different blobstore. Suggested way to migrate blobs is to use third party tool like s3cmd to list and copy all blobs from current blobstore to another. Once copying of all blobs is complete, update config directory to with new blobstore location.


Contribute changes to this page