Redis assets

Command syntax

Pass the Redis command verbatim as command:

• GET mykey
• HGETALL user:1
• SET key value EX 3600
• SCAN 0 MATCH prefix:* COUNT 100

Scope

A Redis asset runs in one of three modes (mode in its config); scope means something different in each.

Standalone and sentinel — scope is the database number (0-15), e.g. scope: "3". Omit it to use the asset's configured database. In sentinel mode every command goes to the master the sentinels currently report.

Cluster — a cluster has only db0; scope is a node address host:port. Each command is routed as follows:

1. Commands that name keys (GET, HGETALL, SET, …) are routed to the master that owns the key's slot; scope is ignored. Multi-key commands whose keys hash to different slots fail with Redis's CROSSSLOT error — use hash tags ({user:1}:a, {user:1}:b) or run them one key at a time.
2. PING, ECHO, TIME, COMMAND … and CLUSTER INFO|NODES|SLOTS|SHARDS|KEYSLOT run on any reachable node when scope is omitted (or on the scope node when given). Other CLUSTER subcommands act on one node (COUNTKEYSINSLOT, RESET, FORGET, FAILOVER, …) and need scope like rule 3.
3. Every other keyless command (SCAN, KEYS, DBSIZE, INFO, CONFIG GET, FLUSHDB, …) only sees one node's data, so it requires scope set to a node, e.g. scope: "10.0.0.2:7002". Without it (or with a db number / unknown address) the call fails and the error lists the current master addresses — pick one and retry, once per master if you need the whole cluster. A replica address is accepted too (useful for read-only diagnostics).

Cluster results carry node (the node that executed the command) and route (key, scope or any) so you can tell how much of the cluster a result covers.

Do NOT send SELECT. It is rejected outright before execution — connections are pooled, so a per-connection database switch would corrupt another caller's selection; a cluster has only db0 anyway. scope is the only correct way to switch databases.

Notes

• Results are returned as JSON.
• Credentials are resolved automatically from the app's encrypted store; never ask the user for a password.

Asset config (for put_asset)

Only the fields of the chosen mode are stored. password and credential_id are mutually exclusive. Plaintext is never returned, is encrypted in the asset, and never creates a managed credential.