registry job from bosh/168
Github source:
5a4f6d9e
or
master branch
Properties¶
aws
¶
access_key_id
¶AWS IAM Access Key ID
ec2_endpoint
¶The service endpoint for Amazon EC2 (optional, if not supplied default region endpoint will be used)
elb_endpoint
¶The service endpoint for Amazon Elastic Load Balancing (optional, if not supplied default region endpoint will be used)
max_retries
¶Max number of retries to connect to AWS
- Default
2
region
¶AWS EC2 Region
secret_access_key
¶AWS IAM Secret Access Key
ssl_ca_file
¶The path to a CA cert bundle in PEM format
ssl_ca_path
¶The path the a CA cert directory
ssl_verify_peer
¶When true the HTTP handler validate server certificates for HTTPS requests
openstack
¶
api_key
¶OpenStack API key
auth_url
¶URL of the OpenStack Identity endpoint to connect to
connection_options
¶Hash containing optional connection parameters to the OpenStack API
endpoint_type
¶OpenStack endpoint type (optional, by default publicURL)
- Default
publicURL
region
¶OpenStack region (optional)
tenant
¶OpenStack tenant name
username
¶OpenStack user name
registry
¶
db
¶
adapter
¶The type of database used
- Default
postgres
connection_options
¶Additional options for the database
- Default
max_connections: 32 pool_timeout: 10
database
¶Name of the registry database
- Default
bosh_registry
host
¶Address of the registry database
password
¶Password used for the registry database
port
¶Port of the registry database
- Default
5432
user
¶Username used for the registry database
- Default
bosh
http
¶
password
¶Password clients must use to access Registry via HTTP Basic Auth
port
¶TCP port Registry daemon listens on
- Default
25777
user
¶Username clients must use to access Registry via HTTP Basic Auth
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/registry/
directory
(learn more).
bin/registry_ctl
(fromregistry_ctl
)config/registry.yml
(fromregistry.yml.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.