Skip to content

Releases: cloudfoundry/bosh-gcscli

v0.0.18

02 Mar 21:53
Compare
Choose a tag to compare
  • Remove whitelisted Google Cloud Storage regions and associated validation between region and storage class. Instead, we will let the google API returns the appropriate error.

v0.0.16

26 Nov 19:28
Compare
Choose a tag to compare
  • Enables generating signed URLs intended to be used with customer-supplied encryption keys

v0.0.14

31 Oct 20:35
Compare
Choose a tag to compare
  • Validate the action argument provided when generating signed urls

bosh-gcscli

26 Oct 01:19
Compare
Choose a tag to compare
  • client will now fall back to using a public GCS client if the authenticated client fails for get or exists. This is needed on GCE where the authenticated client may be an empty default service account. In that scenario we need to use the public GCS client to fetch public blobs. See #17 for more info.
94163f40c10c7f705db1d567beb75d570e3d117a  bosh-gcscli-0.0.5-linux-amd64

bosh-gcscli

25 Oct 23:06
Compare
Choose a tag to compare
  • client API has changed. There is now a single New method that expects a config.GCSClient. For more details see 464c3ab
  • storage_class settings are now only validated on put. This was causing failures when an actor had access to specific objects but not to the bucket settings (eg public objects)
  • Client falls back to none credentials mode when finding the application default credentials fails. This is to address behavior on GCE when the instance has a service account associated but does not have scope to the storage API. This prevented access to public buckets when attempting to fetch a token for authenticating.
  • Client re-attempts "put" operation up to 3 times if it fails to upload
  • Updated documentation/contributing guide
07b7c0696407cea33fc10bb5e95551d7e25aa18cc1993cf2d22f0df6e8e268f2  bosh-gcscli-0.0.4-linux-amd64

Initial Version

27 Jul 16:51
Compare
Choose a tag to compare

This release includes the baseline functionality needed for the BOSH director.

Future releases will be just a tag. A tag of vx.y.z has their binary located at

 https://s3.amazonaws.com/bosh-gcscli/bosh-gcscli-x.y.z-linux-amd64

For example, v0.0.2 has its binary located at

 https://s3.amazonaws.com/bosh-gcscli/bosh-gcscli-0.0.2-linux-amd64

In the future, it is possible to switch from just tags to full releases with the binary, see #14 for more.