Skip to content

fix(query)!: list all resources when no address is given - #125

Open
chalabi2 wants to merge 2 commits into
mainfrom
fix/unscoped-query-lists
Open

chalabi2 wants to merge 2 commits into
mainfrom
fix/unscoped-query-lists

Conversation

@chalabi2

Copy link
Copy Markdown
Contributor

List queries no longer need a default account. With no address, akt q deployment, market order, market bid, market lease and cert list return every matching resource on the network, one page at a time (--limit, default 100), and akt q deployment group gains a matching list mode built from a page of deployments. With a default account set, bare lists are now network-wide too; pass an address to list your own. Unfiltered lists continue with --page-key, since the chain rejects --page and --offset without a state filter.

Verified build, full tests, lint, changelog, offline e2e, coverage of every changed line, and each bare list against mainnet.

Bare list queries refused to run without a default account, and with
one they showed only that account's resources. A query should not need
an account to answer, so with no address the deployment, order, bid,
lease and certificate lists now send an empty owner (and provider under
--by provider), which the chain treats as no filter. The result is one
page, 100 by default. The default account now fills in only the
numeric dseq shorthand.

deployment group gains a list mode for the same reason: with no dseq it
pages through deployments and prints their groups, carrying the page's
pagination in structured output. It refuses --page and --offset because
the chain accepts an offset only with a state filter; the docs and help
text point unfiltered lists at --page-key instead.

BREAKING CHANGE: with a default account configured, a bare list such as
`akt query deployment` now returns every matching resource on the
network instead of that account's. Pass the address to list your own.

Signed-off-by: Joseph Chalabi <chalabi.joseph@gmail.com>
@chalabi2
chalabi2 requested a review from a team as a code owner October 28, 2026 19:56
Keep rate-limit, server and redirect failures typed so nested secret
sanitization retains their status without exposing response bodies.
This lets the live Console CI lane classify failures that previously
appeared only as process_error. Mutation retries remain unchanged.

Signed-off-by: Joseph Chalabi <chalabi.joseph@gmail.com>

This branch is waiting to be deployed

1 waiting deployment
console-sandbox — d421f8f3 Waiting Nov 4, 2026 by chalabi2 via e2e-console-sandbox #311
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant