Jorge Turrado Ferrero

I guess that something isn't wrong with any string generation because there are a lot of errors like this during e2e tests: https://github.com/kedacore/keda/actions/runs/9645629374/job/26600554311#step:9:278 ```bash helper.go:***87: Waiting for successful execution of...

Let me trigger the test again and check the Env vars used

/run-e2e azure_postgresql **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/10075173714)

I think that the approach proposed by @Nohac of having different "matching" rules can bring a lot of flexibility. @tomkerkhove @Eldarrin ?

Ping @tomkerkhove @Eldarrin ?

/skip-e2e

Sorry for the slow response, my life's been a chaos :( I guess that we can include this as another scaler that users can use. I see the potential of...

There is a helm chart we can use to run IBM MQ inside testing clusters https://github.com/ibm-messaging/mq-helm/blob/main/charts/ibm-mq/README.md

Thanks!

Hello! > * Typo while parsing `TriggerMetadata` `tlsDisabled` field . The currently used key is `config.TriggerMetadata["tls"]`. See [`main`/pkg/scalers/ibmmq_scaler.go#L135](https://github.com/kedacore/keda/blob/main/pkg/scalers/ibmmq_scaler.go?rgh-link-date=2024-05-12T14%3A07%3A50Z#L135) And as mentioned in the scaler documentation [kedacore/keda-docs@`main`/content/docs/2.15/scalers/ibm-mq.md](https://github.com/kedacore/keda-docs/blob/main/content/docs/2.15/scalers/ibm-mq.md?rgh-link-date=2024-05-12T14%3A07%3A50Z) `tlsDisabled` is the correct...