vault job from safe/0.3.4
Github source:
24d8b7c or
master branch
Properties¶
safe¶
peer¶
force_bind_default_ip¶Forces Consul agent to bind to the default ip address, necessary when using non RFC1918 space in a private context.
- Default
false
port¶TCP port to use for peer-to-peer communication
- Default
8100
post_start¶
interval¶Seconds between Consul health polls in the post-start script.
- Default
5
timeout¶Seconds the post-start script waits for the local Consul server to become a healthy raft voter in a healthy cluster with one voter per vault instance and a leader. When the wait runs out, post-start fails and BOSH halts the deploy at this instance, before it stops the next Consul server. A brand-new cluster passes while servers that hold no raft data wait for their peers. A stopped cluster that already holds data cannot elect a leader one server at a time, so start every instance at once, for example with
bosh start --canaries=0 --max-in-flight=100%.
- Default
600
tls¶
ca¶TLS CA certificate to use for verifying peer-to-peer communication. If not provided, a self-signed certificate will be automatically generated and used.
certificate¶TLS certificate to use for peer-to-peer communication. If not provided, a self-signed certificate will be automatically generated and used.
key¶TLS private key to use for peer-to-peer communication. If not provided, a self-signed certificate will be automatically generated and used.
use_self_signed_certs¶Indicate whether we generate self-signed peer certificates
- Default
false
verify¶Verify the TLS certificates presented by the Consul backend
- Default
true
port¶TCP port to bind the Vault on. Defaults to 443.
- Default
443
tls¶
certificate¶TLS certificate to use for securing communnication with clients.
key¶TLS private key to use for securing communication with clients.
ui¶If set to true, the Vault UI will be enabled.
- Default
false
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/vault/ directory
(learn more).
bin/consul(frombin/consul)bin/post-start(frombin/post-start)bin/pre-start(frombin/pre-start)bin/strongbox(frombin/strongbox)bin/vault(frombin/vault)config/consul.json(fromconfig/consul.conf)config/vault.config(fromconfig/vault.conf)tls/peer/ca.pem(fromtls/peer/ca.pem)tls/peer/cert.pem(fromtls/peer/cert.pem)tls/peer/key.pem(fromtls/peer/key.pem)tls/vault/cert.pem(fromtls/vault/cert.pem)tls/vault/key.pem(fromtls/vault/key.pem)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/ directory.