fix: add default Operation in Azure Service Bus scaler #6731
Conversation
This file contains hidden or 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
Signed-off-by: Rick Brouwer <[email protected]>
This was referenced Apr 25, 2025
Signed-off-by: Rick Brouwer <[email protected]>
JorTurFer
approved these changes
Apr 26, 2025
|
/run-e2e azure_service_bus |
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.
There was recently a refactor done in Azure Servicebus scaler released in 2.17 that appears to have accidentally removed the logic setting a default value for operation when it is not provided.
This PR should fix this.
Checklist
Fixes #6730