New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor improvement in RabbitMQ executor #1500
base: 4.x
Are you sure you want to change the base?
Minor improvement in RabbitMQ executor #1500
Conversation
ee97ccf
to
8ce2e10
Compare
8ce2e10
to
f50de71
Compare
5c8a9c0
to
38efd8a
Compare
} | ||
|
||
func createQueueIfNecessary(cfg map[string]string, queue string, ch *amqp.Channel) error { | ||
if val, ok := cfg["queue.create"]; !ok || (ok && val == "false") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this query rabbit in order to check if the queue already exists?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we don't need to check if the queue exists here. If the user chooses not to create the queue via the plugin, we expect him to create it manually.
If the user doesn't declare the queue, message publishing will fail with error in logs or a failed execution in UI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM aside from comment
Provide possibility to decide whether to create queues when using RabbitMQ executor and possibility to choose queue's configuration (
durable
,auto_delete
,exclusive
) if user decides to create the queue via plugin.Also allows users to customize message publishing using
messageId
,contentType
anddelivery_mode
options.