Jorge Turrado Ferrero

The errors say that your query is returning multiple elements. Your query has to return a single element in order to work. Maybe it's a bit hidden in the docs...

the error says `prometheus query %s returned multiple elements`. I guess that the error here is clear, but the docs isn't clear enough, but we could modify the message clarifying...

> Was that already done for Azure Event Hubs? not yet, you can do it if you want :)

hey @brainslush Today we have merged [a PR](https://github.com/kedacore/keda/pull/3717) with 2 new e2e test for Event Hub, one for `blobMetadata` strategy and another for `goSdk` strategy. You can create a new...

I agree with @tomkerkhove , we coud just add support to adding additional annotations, how end users use them is their scope. Maybe we could add a section in the...

Hey, I'd say that the problem is related with the ScaledObject length. Is there any option to reduce it? I have created a PR (linked to this issue) but we...

yes, as @tomkerkhove said, we have to think it better so this fix will not be included till v2.8. Meanwhile, you could try reducing the ScaledObject name size 🙏

Yes, but in that case we should add the current name as an annotation IMO to having a simple way to track which is what without inspecting all the SO...

No no, I'm not saying to link them using the annotation in the HPA, I see it as a helper for human discovery, KEDA should continue using the current approach...

Hey @Axory , I'm checking Hashicorp Vault Transit and it seems like encryption as a service more than storing values encrypted. If I'm not wrong, the flow in case of...