fix(redis scaler): use literal command names in Lua script for Alibaba Cloud compatibility

[cxhello]

The Redis scaler's Lua script uses a table lookup variable as the first argument to redis.call(), which fails on Alibaba Cloud Redis Cluster instances that enforce strict Lua script validation requiring literal strings.

Before (fails on Alibaba Cloud Redis Cluster):

local cmd = {
    zset = 'zcard',
    set = 'scard',
    list = 'llen',
    hash = 'hlen',
    none = 'llen'
}
return redis.call(cmd[listType], listName)

After (compatible with all Redis deployments):

if listType == 'zset' then
    return redis.call('zcard', listName)
elseif listType == 'set' then
    return redis.call('scard', listName)
elseif listType == 'hash' then
    return redis.call('hlen', listName)
else
    return redis.call('llen', listName)
end

Checklist

• I have verified that my change is according to the deprecations & breaking changes policy
• Changelog has been updated and is aligned with our changelog requirements, only when the change impacts end users
• Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #7758

[github-actions]

Thank you for your contribution! 🙏

Please understand that we will do our best to review your PR and give you feedback as soon as possible, but please bear with us if it takes a little longer as expected.

While you are waiting, make sure to:

• Add an entry in our changelog in alphabetical order and link related issue
• Update the documentation, if needed
• Add unit & e2e tests for your changes
• GitHub checks are passing
• Is the DCO check failing? Here is how you can fix DCO issues

Once the initial tests are successful, a KEDA member will ensure that the e2e tests are run. Once the e2e tests have been successfully completed, the PR may be merged at a later date. Please be patient.

Learn more about our contribution guide.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[wozniakjan]

/run-e2e redis
Update: You can check the progress here

passed tests: 0

failed tests: 12

Execution of tests/scalers/redis/redis_sentinel_streams_lag/redis_sentinel_streams_lag_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_sentinel_streams_length/redis_sentinel_streams_length_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_cluster_streams_pending_entries/redis_cluster_streams_pending_entries_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_cluster_streams_lag/redis_cluster_streams_lag_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_standalone_lists/redis_standalone_lists_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_cluster_streams_length/redis_cluster_streams_length_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_cluster_lists/redis_cluster_lists_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_standalone_streams_lag/redis_standalone_streams_lag_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_sentinel_streams_pending_entries/redis_sentinel_streams_pending_entries_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_sentinel_lists/redis_sentinel_lists_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_standalone_streams_length/redis_standalone_streams_length_test.go, has failed after "three" attempts
Execution of tests/scalers/redis/redis_standalone_streams_pending_entries/redis_standalone_streams_test_pending_entries_test.go, has failed after "three" attempts

[Copilot]

Pull request overview

This PR updates the Redis scaler’s Lua script to avoid passing a variable/table lookup as the first argument to redis.call, improving compatibility with Alibaba Cloud Redis Cluster’s strict Lua script validation.

Changes:

• Replace Lua table-based command selection (cmd[listType]) with if/elseif branches that call Redis commands via literal strings.
• Add an Unreleased changelog entry documenting the Redis scaler compatibility fix.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
pkg/scalers/redis_scaler.go	Updates the Redis scaler Lua script to use literal command names in redis.call.
CHANGELOG.md	Adds an Unreleased “Redis Scaler” fix entry (but also removes an unrelated AWS scalers entry).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[rickbrouwer]

/run-e2e redis Update: You can check the progress here

@wozniakjan: I don't think this one will succeed; I believe we have some Redis E2E issues (given that all Redis tests fail in both main and E2E).

[wozniakjan]

@wozniakjan: I don't think this one will succeed; I believe we have some Redis E2E issues (given that all Redis tests fail in both main and E2E).

I also suspected that, haven't investigated but thought that maybe randomly this PR fixes it :). If it fails here too then I will troubleshoot the redis e2e tests in main.

EDIT: #7768

[cxhello]

Thanks for the review! Addressed all feedback in the latest push:

1. Restored the accidentally removed AWS Scalers changelog entry
2. Added explicit handling for list/none key types and error_reply for unsupported types (e.g. string, stream)
3. Deduplicated the Redis Scaler changelog entry and kept alphabetical order

[wozniakjan]

/run-e2e redis
Update: You can check the progress here

[JorTurFer]

/run-e2e redis
Update: You can check the progress here

[JorTurFer]

/run-e2e redis
Update: You can check the progress here

passed tests: 12

Execution of tests/scalers/redis/redis_standalone_streams_pending_entries/redis_standalone_streams_test_pending_entries_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_standalone_streams_length/redis_standalone_streams_length_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_standalone_streams_lag/redis_standalone_streams_lag_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_standalone_lists/redis_standalone_lists_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_sentinel_streams_length/redis_sentinel_streams_length_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_cluster_streams_length/redis_cluster_streams_length_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_cluster_streams_pending_entries/redis_cluster_streams_pending_entries_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_cluster_streams_lag/redis_cluster_streams_lag_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_sentinel_lists/redis_sentinel_lists_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_cluster_lists/redis_cluster_lists_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_sentinel_streams_pending_entries/redis_sentinel_streams_pending_entries_test.go, has passed after "one" attempts
Execution of tests/scalers/redis/redis_sentinel_streams_lag/redis_sentinel_streams_lag_test.go, has passed after "one" attempts

failed tests: 0