Refactor IBM MQ scaler and remove and deprecate variables#6034
Refactor IBM MQ scaler and remove and deprecate variables#6034JorTurFer merged 2 commits intokedacore:mainfrom
Conversation
a1db827 to
3e31a12
Compare
|
Hello Could you update the PR to align it with our deprecation policy? I think that unifying is always better |
82f5b89 to
995b612
Compare
I think that is possible. I will work on it and get back to you as soon as possible. |
Thanks. You are absolutely right! I have updated the PR. |
a61368f to
c1d94ce
Compare
wozniakjan
left a comment
There was a problem hiding this comment.
I think the changes for IBM scaler look really good!
ptal @JorTurFer
d8611d8 to
cc3aae8
Compare
|
ptal @kedacore/keda-core-contributors, I think this should be good to merge |
I forgot the |
|
LGTM, just an small nit |
Signed-off-by: Rick Brouwer <rickbrouwer@gmail.com>
|
/run-e2e ibm |
queueManagerparameter is currently checked to see if it's filled, but it's not used elsewhere in the code. This unused code is removed.tlsDisabled(as mentioned in the documentation) /tls(as mentioned in the code) will be announced as being deprecated in a further release. All other scalers use the parameterunsafeSsl. To maintain consistency between other scalers, we are making changes, asunsafeSslalready handles this functionality.tlswill still be supported. When both variables are filled in, an error message is logged and returned. If onlytlsis filled in, its value will be assigned tounsafeSsl. A deprecation info message will be logged. My proposal is to tag thetlsparameter withdeprecated=use unsafeSsl insteadin version 2.18 and remove the deprecated code.Checklist
Fixes #6033
Docs: 1445
Related: 5797