rabbitmq-server job from cf-rabbitmq/341.0.0
Github source:
e845871c
or
master branch
Properties¶
rabbitmq-server
¶
administrators
¶
broker
¶
password
¶RabbitMQ admin password for broker
username
¶RabbitMQ admin username for broker
management
¶
password
¶RabbitMQ admin password for operator
username
¶RabbitMQ admin username for operator
check_queue_sync
¶If true, waits for quorum and mirror queues to sync before stopping the node
- Default
false
cluster_name
¶The cluster_name is used by plugins such as rabbitmq_prometheus and rabbitmq_federation. Warning: do not change the cluster_name across BOSH deployments when federation is already set up.
- Default
""
cluster_partition_handling
¶Cluster partition recover mode property. Valid values are: pause_minority, autoheal
- Default
pause_minority
config
¶RabbitMQ configuration (base64 encoded). If this property is set, rabbitmq-server.load_definitions is ignored.
- Default
W10u
cookie
¶Erlang cookie used by RabbitMQ nodes and rabbitmqctl. You should set this to a secure password
create_swap_delete
¶If true, configure rabbitmq-server to use vm_strategy create-swap-delete (i.e. use RabbitMQ long node names, FQDNs for Rabbit nodes names, and no hosts in erl_inetrc).
- Default
false
disk_alarm_threshold
¶The threshold in bytes of free disk space at which rabbitmq will raise an alarm
- Default
'{mem_relative,0.4}'
erlang_major_version
¶Major version of Erlang to use on RabbitMQ instances in this deployment
- Default
23
fd_limit
¶The file descriptor limit for the RabbitMQ process
- Default
300000
force_cluster_shutdown_on_version_change
¶Force a cluster shutdown in the event of a Erlang major version upgrade, to ensure cluster consistency. This will lead to app downtime.
- Default
false
load_definitions
¶Definitions to be loaded by RabbitMQ at startup. If rabbitmq-server.config is set, this property is ignored.
management_tls
¶
cacert
¶RabbitMQ management CA certificate
cert
¶RabbitMQ management certificate
enabled
¶Use HTTPS listeners on management. Will not accept HTTP connections
- Default
false
key
¶RabbitMQ management private key
oauth
¶
enabled
¶Enables RabbitMQ OAuth plugin
- Default
false
resource_server_id
¶Prefix used for scopes in UAA to avoid scope collisions
- Default
""
signing_key
¶The public key (verification key) of the RSA key pair or the symmetric signing key used by UAA to sign the JWT token
signing_key_id
¶The ID of the JWT signing key to be used when signing tokens.
uaa_client_id
¶The UAA client which presents a valid access_token acquired from UAA as the password in order to authenticate with RabbitMQ.
uaa_location
¶UAA URL (e.g. http://localhost:8080/uaa)
plugins
¶List of RabbitMQ plugins
ports
¶List of ports on which the RabbitMQ cluster accepts connections
ssl
¶
cacert
¶RabbitMQ server CA certificate(s). If there is more than one certificate, they should be concatenated
cert
¶RabbitMQ server certificate
ciphers
¶TLS ciphers to use
disable_non_ssl_listeners
¶Should RabbitMQ reject connections on non-TLS ports when TLS is enabled
- Default
false
enabled
¶Use TLS listeners. Will not accept non-TLS connections
- Default
false
fail_if_no_peer_cert
¶Should RabbitMQ server reject connection if there is no peer cert
- Default
false
key
¶RabbitMQ server private key
verification_depth
¶Peer verification depth used by RabbitMQ server
- Default
5
verify
¶Peer verification method used by RabbitMQ server
- Default
false
versions
¶TLS protocol versions to support
- Default
- tlsv1.2 - tlsv1.1
timeouts
¶
port
¶Server and client timeout for a specific port
version
¶Version of RabbitMQ to use
- Default
"3.8"
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/rabbitmq-server/
directory
(learn more).
bin/add-rabbitmqctl-to-path
(fromadd-rabbitmqctl-to-path.bash
)bin/cleanup-http-logs
(fromcleanup-http-logs.bash
)bin/cluster-check
(fromcluster-check.bash
)bin/drain
(fromdrain.bash
)bin/env
(fromenv.erb
)bin/kill-with-fire
(fromkill-with-fire.bash
)bin/node-check
(fromnode-check.bash.erb
)bin/plugins.sh
(fromplugins.sh.erb
)bin/post-deploy
(frompost-deploy.bash
)bin/post-start
(frompost-start.bash
)bin/pre-start
(frompre-start.bash
)bin/pre-stop
(frompre-stop.bash.erb
)bin/rabbitmq-server.init
(fromrabbitmq-server.init.bash
)bin/setup.sh
(fromsetup.bash
)config/indicators.yml
(fromindicators.yml.erb
)config/prom_scraper_config.yml
(fromprom_scraper_config.yml.erb
)etc/advanced.config
(fromadvanced.config.erb
)etc/cacert.pem
(fromcacert.pem.erb
)etc/cert.pem
(fromcert.pem.erb
)etc/config
(fromconfig.erb
)etc/definitions.json
(fromdefinitions.json.erb
)etc/key.pem
(fromkey.pem.erb
)etc/management-cacert.pem
(frommanagement-cacert.pem.erb
)etc/management-cert.pem
(frommanagement-cert.pem.erb
)etc/management-key.pem
(frommanagement-key.pem.erb
)etc/rabbitmq.conf
(fromrabbitmq.conf.erb
)etc/rabbitmq.config
(fromrabbitmq.config.erb
)etc/users
(fromusers.erb
)lib/delete_old_files.bash
(fromdelete_old_files.bash
)lib/prepare-for-upgrade.bash
(fromprepare-for-upgrade.bash
)lib/rabbitmq-config-vars.bash
(fromrabbitmq-config-vars.bash.erb
)lib/setup-vars.bash
(fromsetup-vars.bash.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.