Jorge Turrado Ferrero

> It would be greatly appreciated if the fix could be backported to v2.7 as we (Grafana Labs, who ❤️ KEDA!) are currently staying one minor version behind for stability....

Another question, are you open to be listed as KEDA users 😄 ? https://github.com/kedacore/keda-docs#become-a-listed-keda-user

@kedacore/keda-core-contributors ? 🔝 🔝

> @kedacore/keda-core-contributors ? https://github.com/kedacore/keda/issues/3644#issuecomment-1245903669

hey @bboreham Do you think this change could be enough? https://github.com/kedacore/keda/pull/3762

Hey, I have reviewed the code and you are right. KEDA gets the secrets for each deployment during the scaler build. I think that you requirement makes sense totally but...

Sure, I'll review during the week, I'm a bit busy atm

I have reviewed the PR 😄 WRTconfigMaps and docs, no worries doing configMaps in another PR, but the docs about secrets should be ready to be merged at the same...

The issue with the stacic checks is because we enforce the grouping of imports: ``` - golang - deps - keda ``` In case of scaledobjectcontroller for instance, you are...

I think that we shouldn't do this. The metric name is an internal KEDA thing that it's used to avoid conflicts. Previously we gave the option to "customize it" to...