Skip to content

Restore the listing and export flag docs - #30

Merged
wayneeseguin merged 2 commits into
developfrom
restore-listing-flag-docs
Jul 29, 2026
Merged

Restore the listing and export flag docs#30
wayneeseguin merged 2 commits into
developfrom
restore-listing-flag-docs

Conversation

@wayneeseguin

Copy link
Copy Markdown
Contributor

The two documentation commits from #29 are not on develop.

#29 was stacked on ls-escaped-paths and was never retargeted, so merging
it put its commits on that branch — which #28 had already merged a moment
earlier — rather than on develop. GitHub reports #29 as merged, and it is:
into a branch nothing reads. git merge-base --is-ancestor d67732d origin/develop says no.

This cherry-picks the two commits onto develop unchanged. The content is
the one that was reviewed in #29:

  • the flags on ls, tree, and paths, including the liveness check that
    decides whether a secret is listed at all, and what -q skips

  • what export -a and -d each change, measured against a live Vault
    rather than inferred from the help text — -d also pulls in secrets a
    plain export skips entirely, which the help text does not say

No code changes, so nothing to verify beyond make check, which is green.

The three listing commands took flags the reference never mentioned,
including the one that governs whether a secret appears at all: a
secret whose newest version has been deleted is left out unless -q is
given, even when an older version of it is still readable.
Both flags change which secrets come out, not only how many versions
of each, and neither was described in the reference.
@wayneeseguin
wayneeseguin merged commit ca72ae1 into develop Jul 29, 2026
@wayneeseguin
wayneeseguin deleted the restore-listing-flag-docs branch July 29, 2026 16:39
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