locket job from diego/2.29.0
Experimental: use the BOSH Process Manager to manage the Locket process.
maximum number of open connections to the database
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
address at which to serve debug info
address at which to serve API requests
Bundle of CA certificates for the Locket 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
Whether to require SSL for Locket communication to the SQL backend
Enable the Locket server to register itself as a service with Consul, for client discovery via Consul DNS. Do not disable without arranging alternate service discovery.
Format for timestamp in component logs. Valid values are ‘unix-epoch’ and ‘rfc3339’.
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.
ca cert for locket server mutual auth tls
server cert for locket server mutual auth tls
server key for locket server mutual auth tls
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