bbs job from diego/2.29.0
Experimental: use the BOSH Process Manager to manage the BBS process.
When set, the BBS will detect Diego cells registered with the Locket API.
Whether to verify the identity of the database host when connecting with TLS. Set this to
falseto allow TLS connections to database providers that do not configure the database’s TLS certificate to include its hostname or IP, such as Google Cloud SQL
Label of the encryption key to be used when writing to the database
Suffix for the BBS advertised hostname
Hostname and port of the auctioneer API, without URI scheme.
CA cert for communication to the auctioneer.
Client cert for communication to the auctioneer.
Client key for communication to the auctioneer.
Whether to require mutual TLS for communication with the auctioneer API. Deprecated, Diego V2 and later require Auctioneer communication to use TLS. This is only relevant when upgrading from V1 to ensure no downtime during the upgrade
REQUIRED: PEM-encoded CA certificate
completed, unresolved tasks are deleted after this duration in seconds
unclaimed tasks are marked as failed, after this duration in seconds
the interval, in seconds, between kicks to tasks in seconds
the interval between runs of the converge process
address at which to serve debug info
Whether the BBS should detect Diego cell registrations present in the Consul key-value store. To prevent unexpected loss of capacity, set to ‘false’ only when the BBS uses Locket and when all Diego cells in the cluster maintain their registrations via Locket.
Enable access log, i.e. log every request made to the bbs
List of encryption keys to be used
address at which BBS serves ‘/ping’ health-check endpoint
address at which to serve API requests
Hostname and port of the Locket server. When set, the BBS attempts to claim a lock from the Locket API and will detect Diego cells registered with the Locket API.
CA cert for communication to the rep.
Client cert for communication to the rep.
Client key for communication to the rep.
capacity of the tls client cache
Whether to require TLS for communication to the securable rep API server. Deprecated, Diego V2 and later require Rep communication to use TLS. This is only relevant when upgrading from V1 to ensure no downtime during the upgrade
REQUIRED: PEM-encoded client certificate
REQUIRED: PEM-encoded client key
Set to ‘true’ for the BBS to skip acquiring a Consul lock. Requires ‘diego.bbs.locket.api_location’ to be set.
Bundle of CA certificates for the BBS to verify the SQL server SSL certificate when connecting via SSL
Database driver to use for SQL backend (for example: mysql,postgres)
Host for SQL backend
Password to use for connecting to SQL backend
Port for SQL backend
Database name to use for connecting to SQL backend
Username to use for connecting to SQL backend
Maximum number of idle connections to the SQL database
Maximum number of open connections to the SQL database
Whether to require SSL for BBS communication to the SQL backend
Enable the BBS to register itself as a service with Consul, for client discovery via Consul DNS. Do not disable without arranging alternate service discovery.
Maximum number of files (including sockets) the BBS process may have open.
Format for timestamp in component logs. Valid values are ‘unix-epoch’ and ‘rfc3339’.
Length in bytes above which logged strings will be truncated. If set to 0, turns off truncation.
CA Cert used to communicate with local metron agent over gRPC
Cert used to communicate with local metron agent over gRPC
Key used to communicate with local metron agent over gRPC
True to use local metron agent gRPC v2 API. False to use UDP v1 API.
Local metron agent gRPC port
Enable tuning /proc/sys kernel parameters. NOTE: set this property to ‘false’ when deploying to BOSH-Lite or other containerized BOSH clouds.
Experimental: The number of times task placement should be retried after pre-execution task failure.
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be