broker job from on-demand-service-broker/0.1.0
Github source:
614f672b
or
master branch
Properties¶
broker
¶
bosh
¶
authentication
¶
basic
¶password
¶BOSH director password
username
¶BOSH director username
uaa
¶client_id
¶UAA client ID
client_secret
¶UAA client secret
url
¶UAA URL
director_uuid
¶BOSH director UUID
url
¶BOSH URL
cf_route
¶
nats
¶
host
¶CF NATS host:port
- Default
""
password
¶password for NATS
- Default
""
username
¶username for NATS
- Default
""
subdomain
¶subdomain for broker
- Default
""
password
¶Broker basic auth password
port
¶Port for the broker
- Default
8080
service_adapter
¶
path
¶the path to the service adapter binary located on the host with the broker
service_catalog
¶
bindable
¶is service bindable?
id
¶service ID for CF marketplace
metadata
¶
display_name
¶apps manager display name
- Default
""
plan_updatable
¶are plan migrations allowed?
plans
¶the service plans to be presented to Cloud Foundry
requires
¶string array of permissions required by broker
- Default
[]
service_description
¶service description for CF marketplace
service_name
¶service offering for CF marketplace
tags
¶string array of tags for catalog
- Default
[]
service_deployment
¶
releases
¶releases to deploy for each instance
stemcell
¶
os
¶stemcell OS to use for every job in the service deployment
version
¶stemcell version to use for every job in the service deployment
sqlite_db_path
¶Path to sqlite database
- Default
/var/vcap/store/broker-db/store.db
username
¶Broker basic auth username
cf
¶
system_domain
¶cloud foundry system domain
- Default
""
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/broker/
directory
(learn more).
bin/broker-ctl.sh
(frombroker-ctl.sh.erb
)bin/register-route-ctl.sh
(fromregister-route-ctl.sh.erb
)config/broker.yml
(frombroker.yml.erb
)config/register-route.yml
(fromregister-route-config.yml.erb
)dbconf/dbconf.yml
(fromdbconf.yml.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.