Jorge Turrado Ferrero

I thought that there was a feature request to support encrypted json to parse the json and pass a given item from inside the json to the scaler. I think...

Hello Sorry for the delay, my life has been complicated, I've assigned it to you! Thanks a lot

I think that nobody is working on this at the moment. I can assign it to you if you are still interested I think that the feature is to support...

>I believe I need to add the AwsSecretManagerJson to the CRD. I have not directly worked on CRDs before. I pointer would help. To include this new field in the...

I'm checking the documentation of this integration more in depth, and I'm not sure if KEDA already supports this. I mean, KEDA supports reading secrets in json format, just setting...

> Since the RDS secret is a JSON string That was my last comment about, IDK if the RDS secret is just a simple JSON stored as the typical JSON...

The point is that given the current architecture, I'm not sure if adding a new field is a good idea or just an extra effort for end users. I'd see...

Do you mean to document the current code or so?

WDYT @tomkerkhove @zroubalik ? Maybe we can split the CRDs into a new fully isolated chart and deploy that chart as dependency of KEDA (managed by a flag). This could...

No no, I meant the CRDs chart as KEDA chart dependecy, not KEDA as user dependency