RabbitMQ 绑定规范
Detailed documentation on the RabbitMQ binding component
Component format
To setup RabbitMQ binding create a component of type bindings.rabbitmq
. See this guide on how to create and apply a binding configuration.
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.rabbitmq
version: v1
metadata:
- name: queueName
value: queue1
- name: host
value: amqp://[username][:password]@host.domain[:port]
- name: durable
value: true
- name: deleteWhenUnused
value: false
- name: ttlInSeconds
value: 60
- name: prefetchCount
value: 0
- name: exclusive
value: false
- name: maxPriority
value: 5
Warning
以上示例将 Secret 明文存储。 更推荐的方式是使用 Secret 组件, here。
Spec metadata fields
字段 | Required | Binding support | Details | Example |
---|---|---|---|---|
queueName | Y | Input/Output | The RabbitMQ queue name | “myqueue” |
host | Y | Input/Output | The RabbitMQ host address | “amqp://[username][:password]@host.domain[:port]” |
durable | N | Output | Tells RabbitMQ to persist message in storage. Defaults to “false” | “true” , “false” |
deleteWhenUnused | N | Input/Output | Enables or disables auto-delete. Defaults to “false” | “true” , “false” |
ttlInSeconds | N | Output | Set the default message time to live at RabbitMQ queue level. 如果此参数为空,消息将不会过期,继续在队列上存在,直到处理完毕。 See also | 60 |
prefetchCount | N | Input | Set the Channel Prefetch Setting (QoS). 如果此参数为空,QOS 会设置为0为无限制。 | 0 |
exclusive | N | Input/Output | Determines whether the topic will be an exclusive topic or not. Defaults to “false” | “true” , “false” |
maxPriority | N | Input/Output | Parameter to set the priority queue. If this parameter is omitted, queue will be created as a general queue instead of a priority queue. Value between 1 and 255. See also | “1” , “10” |
Output bindings
This component supports both input and output binding interfaces.
字段名为 ttlInSeconds
。
create
输出绑定支持的操作
可以在队列级别 ( 如上所述) 或消息级别定义生存时间。 在消息级别定义的值会覆盖在队列级别设置的任何值。
若要设置在消息级别生存的时间,请使用 metadata
请求正文中的元数据部分。
字段名为 ttlInSeconds
。
示例:
curl -X POST http://localhost:3500/v1.0/bindings/myRabbitMQ \
-H "Content-Type: application/json" \
-d "{
\"data\": {
\"message\": \"Hi\"
},
\"metadata\": {
\"ttlInSeconds\": "60"
},
\"operation\": \"create\"
}"
curl -X POST http://localhost:3500/v1.0/bindings/myRabbitMQ \
-H "Content-Type: application/json" \
-d '{
"data": {
"message": "Hi"
},
"metadata": {
"ttlInSeconds": "60"
},
"operation": "create"
}'
相关链接
Priority can be defined at the message level. If maxPriority
parameter is set, high priority messages will have priority over other low priority messages.
To set priority at message level use the metadata
section in the request body during the binding invocation.
The field name is priority
.
示例:
curl -X POST http://localhost:3500/v1.0/bindings/myRabbitMQ \
-H "Content-Type: application/json" \
-d "{
\"data\": {
\"message\": \"Hi\"
},
\"metadata\": {
"priority": \"5\"
},
\"operation\": \"create\"
}"
curl -X POST http://localhost:3500/v1.0/bindings/myRabbitMQ \
-H "Content-Type: application/json" \
-d '{
"data": {
"message": "Hi"
},
"metadata": {
"priority": "5"
},
"operation": "create"
}'
相关链接
- Basic schema for a Dapr component
- Bindings building block
- 如何通过 input binding 触发应用
- How-To:使用绑定与外部资源进行交互
- 绑定API 参考
Last modified January 1, 0001