Support for managed Redis cloud services with restricted commands (Oracle OCI, AWS ElastiCache, Azure, GCP)

[jgaliana66]

Currently, the langgraph-checkpoint-redis library requires executing the MODULE LIST command during initialization setup(), to check for the presence of modules like RedisJSON and RediSearch.

In managed Redis cloud services (Oracle OCI Cache, AWS ElastiCache, Azure Cache, Google Memorystore), users typically have restricted permissions and cannot execute administrative commands such as MODULE LIST. This results in permission errors and blocks the checkpointer initialization, even if the required modules are installed and active.

Impact:

It is not possible to use LangGraph with Redis persistence in these cloud environments, even if Redis is compatible and the modules are present.
The error affects any cloud deployment where administrative commands are restricted by the provider.

Proposal:

Add a configuration option (e.g., skip_module_check=True) to disable module checking during initialization, allowing basic persistence in restricted environments.
Alternatively, catch the permission error and continue if only basic checkpointing is required.

Use cases:

Oracle OCI Cache (standalone, Redis 7.x): MODULE LIST is blocked by security policy.
AWS ElastiCache: administrative commands are restricted.
Azure Cache for Redis (Standard): restricted commands, only Enterprise allows advanced modules.
GCP Memorystore: does not allow installing or querying modules.

References:

https://docs.oracle.com/en-us/iaas/Content/ocicache/restrictedcommands.htm
http://github.com/redis-developer/langgraph-redis/releases

Would it be possible to add support for this scenario in future versions?

[bsbodden]

@jgaliana66 Unfortunately, those systems are no longer in line with Redis OSS, which began in version 8 to include the formerly separate modules as part of the core offering. We strive to utilize as much of Redis as possible to enhance our integrations with performance, scalability, and resilience. The Redis Query Engine and JSON datatypes are now integral to providing the best possible experience. Until these systems return to full Redis OSS compliance, this would not be possible.