Skip to content

consider removing jq dependence for workflows #424

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jreiberkyle opened this issue Mar 30, 2022 · 1 comment
Open

consider removing jq dependence for workflows #424

jreiberkyle opened this issue Mar 30, 2022 · 1 comment
Labels
2024-revisit SDK committee reviewed and marked for follow-up enhancement

Comments

@jreiberkyle
Copy link
Contributor

Some workflows involving the CLI depend on jq e.g. to extract an order id from the order description printed by planet orders create. Consider cost/benefit of removing jq dependence, e.g. with an option for only printing the order id.

Ref: #383 (comment)

@jreiberkyle jreiberkyle added this to the V2 Post-Release milestone Mar 30, 2022
@ischneider ischneider added the 2024-revisit SDK committee reviewed and marked for follow-up label Jul 25, 2024
@ischneider
Copy link
Member

ischneider commented Jul 25, 2024

In discussion, we decided that there are 2 actionable aspects to this ticket:

  • reduce reliance of jq in CLI docs (especially for introductions) but recognize in the spirit of unix, composition allows extensibility
  • when possible, offer builtin functionality for common filtering, e.g. rather than --ids-only (or such) allow flexibility via partial responses either by field mask or view options https://google.aip.dev/157

And when possible, improve APIs themselves and pass partial response options rather than client-side filtering

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2024-revisit SDK committee reviewed and marked for follow-up enhancement
Projects
None yet
Development

No branches or pull requests

2 participants