Jorge Turrado Ferrero

This is still available, but I'm not sure if this other could be related covering this one https://github.com/kedacore/keda/issues/4694 @tomkerkhove ?

Hi, Sadly, it's not possible atm because the Azure Pipelines API doesn't support it, the only authentication method supported is the PAT. Once AzPipelines team release another mechanism, we can...

Yes we do, and we have had a problem with an expired PAT this week xD I think this feature is really useful and we should add it. In tandem...

[This feature has been already merged](https://github.com/kedacore/keda/pull/4867) and shipped as part of v2.13, so I close the issue

> Just a side note, we shouldn't rely on validation webhooks that much. If possible, this should work withouth validation as well. I have to disagree with this point. KEDA...

LGTM but let's wait until @zroubalik and @tomkerkhove agree with it (or not xD), because this moves the responsibility from the operator to webhooks

> @JorTurFer could you please look at this? We should resolve this already :) Thanks I reviewed here: https://github.com/kedacore/keda/pull/5142#issuecomment-1821669062 From my perspective, webhooks have to validate the information and the...

We should push this topic @zroubalik @tomkerkhove

Hello, What manifest are you using to deploy KEDA? There are 2 flavors, with and without webhooks and maybe there is any failure on them

There are 3 different yaml inside the release: - keda-2.12.0-core.yaml - keda-2.12.0-crds.yaml - keda-2.12.0.yaml Which are you using?