Skip to content

Conversation

@Zerpet
Copy link
Member

@Zerpet Zerpet commented Mar 24, 2022

Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed
Note to contributors: remember to re-generate client set if there are any API changes

Summary Of Changes

We were allowing non-durable quorum queues as a valid manifest. This results in a 400
response from RabbitMQ server. The error is not visible to the user,
until they describe the queue and observe the status condition. Now it
fails sooner, which is good given that we know these settings will never
succeed.

We were allowing non-durable quorum queues, which results in a 400
response from RabbitMQ server. This was not very visible by the user,
until it described the queue and observed the status condition. Now it
fails sooner, which is good given that we now these settings will never
succeed.

Signed-off-by: Aitor Perez Cedres <[email protected]>
Copy link
Contributor

@ChunyiLyu ChunyiLyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great!

@Zerpet Zerpet merged commit f914818 into main Mar 24, 2022
@Zerpet Zerpet deleted the validate-queue-options branch March 24, 2022 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants