Skip to content

epic: JMESPath — jpx-engine migration, query files, introspection #726

@joshrotenberg

Description

@joshrotenberg

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

  • Support @file syntax for JMESPath queries #593 -- Support @file syntax for JMESPath queries
  • Ship pre-built FOCUS queries for cost-report analysis (top-N resources, cost-by-region, cost-by-charge-category, etc.)
  • Named query store (define, run, list) -- enabled by jpx-engine's query store API

Introspection

  • redisctl jmespath functions -- list available functions by category
  • redisctl jmespath describe <fn> -- show function signature, description, examples
  • redisctl jmespath search <keyword> -- fuzzy search for functions

Integration

  • Audit all commands that accept -q / --query and ensure consistent behavior
  • Better error messages for invalid expressions (jpx-engine provides source spans)
  • Consider MCP tool for JMESPath evaluation (would let agents query/transform data in-context)

Key Paths

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    cliRelated to CLI UX and commandsepicParent issue tracking multiple related issues

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions