Jorge Turrado Ferrero

Interesting update :smile: @kedacore/keda-core-contributors , do you think that we should get rid of the GCP Scalers or just use them as wrapper on top of the prometheus one to...

I'm not 100% sure about the right solution, let's talk about this during next standup @zroubalik @wozniakjan

I agree with that, IMHO we should deprecate the GCP scalers and document how to use the prometheus scaler as replacement

I'm reading the things with calm, and it looks that the API will be the same, the stackdriver one, but just the querying language changes, so maybe pushing users to...

We don't expose the underlaying query to endusers, they just introduce the metrics and conditions, and KEDA builds de query using the querying language. That's why I said that maybe...

I've been testing the change in [this PR](https://github.com/kedacore/keda/pull/6968/files) and the change isn't just update the querying. [The API that has to be used changes](https://discuss.google.dev/t/promql-monitoring-queries-via-api/109343), so using the Prometheus Scaler is...

Hello That's a real good point! We won't remove the the current GCP scalers so current users aren't forced to migrate if they don't want. The point is that sometimes...

The image was created but GH creates them as private by default, now it's public

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

Do we need to update the policy to include any extra permission? https://github.com/kedacore/testing-infrastructure/blob/main/terraform/modules/aws/iam/main.tf#L88-L96 If yes, could you open a PR there?