This topic gives you reference information about the Google Storage Bucket service (csb-google-storage-bucket). It details the plans, configuration parameters, and binding credentials.
Caution The Google Storage Bucket service offering is currently in beta and is intended for evaluation and test purposes only. Do not use this product in a production environment.
The table below lists the plans for Google Storage Bucket:
Plan | Description |
---|---|
private | Private Storage bucket |
public-read | Public-read Storage bucket |
When configuring Cloud Service Broker for GCP you can add additional plans. For how to configure plans, see Configure Services with Cloud Service Broker for GCP.
The following table lists parameters which can only be configured for additional plans:
Parameter Name | Values | Default |
---|---|---|
name * |
The plan name | n/a |
id * |
A unique GUID | n/a |
description * |
Description of the new plan | n/a |
display_name |
Name to use when displaying plan in marketplace | n/a |
free |
When false, Service Instances of this Service Plan have a cost | true |
bindable |
Specifies whether Service Instances of the Service Plan can bind to applications | true |
plan_updateable |
Whether the Plan supports upgrade/downgrade/sidegrade to another version | true |
acl |
Storage bucket ACL, see the Google documentation | n/a |
* Required
You can also add any of the configuration parameters listed in the parameters section to your plan.
Note If you set a parameter at plan level, developers cannot change the value when creating or updating service instances.
You can provision a service by running:
cf create-service csb-google-storage-bucket PLAN-NAME SERVICE-INSTANCE-NAME -c '{"PARAMETER-NAME": "PARAMETER-VALUE"}'
You can update the configuration parameters for a service instance by running:
cf update-service SERVICE-INSTANCE-NAME -c '{"PARAMETER-NAME": "PARAMETER-VALUE"}'
The following table lists the parameters that you can configure, by using the -c
flag, when provisioning a csb-google-storage-bucket service:
Parameter Name | Type | Description | Default | Operation |
---|---|---|---|---|
name |
string | The name of the bucket to create. | csb-INSTANCE-ID |
provision and update |
storage_class |
string | The Storage Class of the new bucket. STANDARD , MULTI_REGIONAL , REGIONAL , NEARLINE , or COLDLINE . |
STANDARD |
provision and update |
region |
string | The region of the bucket instance. | us-central1 |
provision and update |
credentials |
string | The GCP credentials. | The value the operator entered for Credentials in Ops Manager. | provision and update |
project |
string | The GCP project to use. | The value the operator entered for Project in Ops Manager. | provision and update |
You can bind a service by running:
cf bind-service APP-NAME SERVICE-INSTANCE --binding-name BINDING-NAME -c '{"PARAMETER-NAME": "PARAMETER-VALUE"}'
The following table lists the parameters that you can configure, by using the -c
flag, when binding to a csb-google-storage-bucket service:
Parameter Name | Type | Description | Default |
---|---|---|---|
role |
string | (Required) The role for the account without the "roles" prefix. For more information, see the Google Cloud documentation. Your operator can override the default enumeration. Options are roles/storage.objectAdmin , roles/storage.objectCreator , and roles/storage.objectViewer . |
n/a |
credentials |
string | The GCP credentials. | The value the operator entered for Credentials in Ops Manager. |
project |
string | The GCP project to use. | The value the operator entered for Project in Ops Manager. |
The format for binding credentials for Google Storage Bucket is as follows:
{
"bucket_name" : "BUCKET-NAME",
"id" : "BUCKET-ID",
"Credentials" : "SERVICE-ACCOUNT-CREDENTIALS",
"Email" : "SERVICE-ACCOUNT-EMAIL",
"Name" : "SERVICE-ACCOUNT-NAME",
"PrivateKeyData" : "SERVICE-ACCOUNT-PRIVATE-KEY",
"ProjectId" : "GCP-PROJECT-ID",
"UniqueId" : "SERVICE-ACCOUNT-UNIQUE-ID"
}