dcloud deploy rabbitmq bindBind a managed RabbitMQ broker as one of its users (private, in the app’s VPC)
Generates {prefix}AMQP_URL (amqps://user:password@<broker address>:5671/%2F — the balancer with 3 nodes), AMQP_HOSTS (every node:5671, for clients that take a list), AMQP_USERNAME, AMQP_PASSWORD and AMQP_CA_FILE (the platform CA in the container) at every rollout. Needs secrets:GetSecretValue on the user’s password. A bound user cannot be deleted. Saving does not restart the app. Pass redeploy: true to roll the live deployment’s own source onto the new configuration (also needs deploy:DeployApp); otherwise the response and GET …/env report pending until someone redeploys.
Synopsis
dcloud deploy rabbitmq bind id --broker-id brokerId --user-name userName [flags]Arguments
<id>Requiredstring
Also accepted as
--id. Constraints: uuid
Flags
--broker-idRequiredstring
The managed RabbitMQ broker to bind
Constraints: /^rmq-[0-9a-f]{12}$/
--user-nameRequiredstring
The broker user the app signs in as
Constraints: /^[a-z][a-z0-9_.-]{0,63}$/
--env-prefixOptionalstring
Put in front of every generated variable name (e.g. CACHE_ gives CACHE_REDIS_URL), so one app can hold several bindings of a kind; default empty
Constraints: max 32 chars, /^([A-Z][A-Z0-9_]*_)?$/
--redeployOptionalboolean (--redeploy / --no-redeploy)
Also roll the live deployment onto the new configuration; default false
Example
dcloud deploy rabbitmq bind id --broker-id example --user-name exampleGenerated from the API description, the same one the API checks requests against and the CLI is built from.