Proposal
In KEDA 2.17.2, the temporal-namespace header is attached to all requests to the temporal server only if the scaler is configured with an API key: https://github.com/kedacore/keda/blob/v2.17.2/pkg/scalers/temporal.go#L220
I would like the scaler to attach the temporal-namespace header to all requests to the temporal server by default, even if the scaler is not configured with an API key.
Use-Case
In our Temporal setup, we don't require the scaler to need API keys (we have an alternate method of authentication), but we do need the scaler to send the temporal-namespace header. This forces us to create ScaledObjects with a apiKeyFromEnv with a fake value in order to get the scaler to send the header. Some of our users find this confusing.
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
No response
Proposal
In KEDA 2.17.2, the
temporal-namespaceheader is attached to all requests to the temporal server only if the scaler is configured with an API key: https://github.com/kedacore/keda/blob/v2.17.2/pkg/scalers/temporal.go#L220I would like the scaler to attach the
temporal-namespaceheader to all requests to the temporal server by default, even if the scaler is not configured with an API key.Use-Case
In our Temporal setup, we don't require the scaler to need API keys (we have an alternate method of authentication), but we do need the scaler to send the
temporal-namespaceheader. This forces us to createScaledObjectswith aapiKeyFromEnvwith a fake value in order to get the scaler to send the header. Some of our users find this confusing.Is this a feature you are interested in implementing yourself?
Yes
Anything else?
No response