Overview
Overhaul the JMESPath subsystem in redisctl. The current setup (jmespath + jmespath_extensions crates) is outdated. jpx-engine provides 400+ functions, better error messages, and is the same engine powering the jpx CLI and MCP server. This is a full rethink, not an incremental patch.
Goals
- Migrate to jpx-engine as the JMESPath backend
- Ship pre-built query files for common analysis patterns (cost reports, resource inventory)
- Add query introspection commands for discoverability
- Consistent JMESPath experience across CLI, MCP server, and jpx tools
Sub-Issues
Core Migration
Query Files
Introspection
Integration
Key Paths
References
Overview
Overhaul the JMESPath subsystem in redisctl. The current setup (
jmespath+jmespath_extensionscrates) is outdated.jpx-engineprovides 400+ functions, better error messages, and is the same engine powering the jpx CLI and MCP server. This is a full rethink, not an incremental patch.Goals
Sub-Issues
Core Migration
jmespath+jmespath_extensionswithjpx-engine)Query Files
Introspection
redisctl jmespath functions-- list available functions by categoryredisctl jmespath describe <fn>-- show function signature, description, examplesredisctl jmespath search <keyword>-- fuzzy search for functionsIntegration
-q/--queryand ensure consistent behaviorKey Paths
Cargo.tomldependencies onjmespath+jmespath_extensionsReferences