Support multiple queues at the IBMMQ scaler #6182
Open
+56
−44
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rickbrouwer
force-pushed
the
issue-6181
branch
from
5a9617c
to
8651e67
Compare
rickbrouwer
force-pushed
the
issue-6181
branch
3 times, most recently
from
593c9db
to
afd816d
Compare
Signed-off-by: rickbrouwer <rickbrouwer@gmail.com>
rickbrouwer
force-pushed
the
issue-6181
branch
from
afd816d
to
9d2717a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed the
queueNameparameter so that it accepts multiple queues (comma (,) separated). The code is is changed so it's request the current depth per queue and only use the current depth from the queue with the most messages.Checklist
Fixes #6181
Docs: kedacore/keda-docs#1473