Jorge Turrado Ferrero

https://github.com/kedacore/keda/issues/3205

@mknet3 , ping me if you need help ;)

@mknet3 prefer to keep it free for the moment because it's his first task with golang

@adborroto , @xoanmm Maybe anyone of you is interested on this 😉

What do you think if we use this change to unify those parameters? I mean, we can rename all of them into threshold/activationThreshold and keep the consistency accros all the...

Related with this issue, [during the last standup](https://docs.google.com/document/d/1zdwD6j86GxcCe5S5ay9suCO77WPrEDnKSfuaI24EwM4/edit#heading=h.tf14cpkj21cz) we decided to continue with it for all scalers, and we also agree with using `activation*` as a prefix for every scaler...

When are we going to remove this? maybe we could follow k8s deprecation policies, WDYT?

@raorugan , I'm going to tackle this :)

Maybe we can simplify the current approach and code just having 2 ways for reading all the variables: - metadata + env + auth - env + auth We could...

Sure, right now, we support reading the values from environment, metadata and also triggerauthentication. The thing is that not all parameters can be recovered from all sources and there could...