Jorge Turrado Ferrero

I can confirm this case. From my super newbie side, who should replace the env vars? The target allocator before exposing the value or the collector after reading the value?...

Could you share your ScaledObject (and your trigger authentication)? just remove the sensitive data please From logs I see a lot of 401 errors

This feature would be nice!

We are also interested on this as it's useful in case of a cluster has been accidentally deleted to recreate the ArgoCD cluster just replacing the old one (the `--upsert`...

Yeah, that's correct, but in that scenario, terraform tries to update the cluster in ArgoCD and it doesn't use the modifier `--upsert` (like the cli supports), so terraform creates the...

> Just so I'm clear... You're saying that if a cluster (that was created via Terraform) is deleted outside of Terraform, then the provider will try to update the non-existent...

This is quite nice definition for the current issue, yeah. Great! ❤️

Hello, In KEDA ([keda.sh](https://keda.sh)) we support HashiCorp Vault as secrets source (we just read values from there as a client), due to it, we use these deps: ``` github.com/hashicorp/vault/api github.com/hashicorp/errwrap...

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

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