Consider using an improved JMESPath library

[springcomp]

More than a feature request, this issue is my formal way to introduce JMESPath Community.

For many months we at JMESPath Community worked on brainstorming ideas for new features and curated a reasonably scoped set of new features as our first milestone.

The goal is to pick the JMESPath language were it left off and steward improvements to the specification at a quicker pace with a clear governance.

Amongst the new features being proposed one can find:

• Arithmetic expressions : allowing simple numeric operations.
• String manipulation functions.
• Ability to refer to arbitrary lexical scopes.
• and more.

As we are wrapping up and nearing completion of this first batch of improvements, we are publishing release candidates of the Python implementation of the spec.

If those sound like useful features for az CLI, I would like to enquire about the required steps and process to have this library included as a dependency to this repository.

I would be happy to submit a pull request in due course obviously. Please let me know if that is something you would consider.

[yonzhan]

@jiasli for awareness

[springcomp]

FYI jmespath-community/1.1.0rc2 has been published.
This marks the final release candidate before publishing the final release version in a few weeks.

[springcomp]

FYI, jmespath-community/1.1.0 has been released.
This marks the official first milestone of JMESPath Community.

[Miraj50]

@springcomp I was looking for string manipulation functions for case-insensitive search and it seems it's not available in az cli as of today. From what I understand, these features are already available, but Azure CLI is still on an older version of JMESPath. Am I correct?

@jiasli @yonzhan Is there a plan on upgrading Azure CLI to support these new really helpful features of JMESPath?

[springcomp]

@Miraj50 string manipulation functions is available in JMESPath Community.

Case-insensitive search is not, however.
This feature is subject to feedback and acceptance on those two PRs:

• knack#272
• Consider using an improved JMESPath library #24542

[jiasli]

@Miraj50, please see my comment at #25590 (comment).

For now, please consider piping Azure CLI's output to jp or jq for advanced parsing.