Skip to content

Conversation

@Zerpet
Copy link
Member

@Zerpet Zerpet commented May 27, 2024

This closes #822

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

Queue arguments can't be updated in RabbitMQ. The webhook now disallows updates on queue arguments, matching the behaviour of RabbitMQ.

@Zerpet Zerpet self-assigned this May 27, 2024
@Zerpet Zerpet added this to the v1.14.2 milestone May 27, 2024
Zerpet added 2 commits May 28, 2024 09:37
Queue arguments can't be updated in RabbitMQ. The webhook now disallows updates on queue arguments, matching the behaviour of RabbitMQ. Signed-off-by: Aitor Perez Cedres <1515757+Zerpet@users.noreply.github.com>
There is little value in running vuln in unit-tests. When it complains, it complains about CVEs in your local Go version, which is not the same Go binary that will build in CI (we use stable and oldstable). The target `git-commit-sha` was a no-op. The logic to determine whether to add a `-` at the end of the commit SHA was broken, it was always chosing to add a `-`. Now the `GIT_COMMIT` is always the HEAD commit SHA + `-dev` suffix. Signed-off-by: Aitor Perez Cedres <1515757+Zerpet@users.noreply.github.com>
@Zerpet Zerpet force-pushed the fix/inmutable-queue-args branch from 6d89906 to f13f359 Compare May 28, 2024 08:45
@Zerpet Zerpet merged commit 1a93d84 into main May 28, 2024
@Zerpet Zerpet deleted the fix/inmutable-queue-args branch May 28, 2024 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

4 participants