Skip to content

tally v0.5.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 14:55
· 2 commits to main since this release
v0.5.0
3351edd
  • Locations can be added to an existing key. tally locate ID --location KIND:REF records another copy without
    rewriting the entry by hand.

  • The entry field table names rotated. tally rotated writes the rotation date there, a key rotated elsewhere can
    record it by hand, check does not warn on it, and the key's issue shows it as the last rotation.

  • Keys an organization owns can go to a person. Set the action's org-assignee input, or
    TALLY_ORG_ASSIGNEE, to a handle, and their issues are assigned to it with no org-owner gap. A repository
    that keeps personal handles out of its tree can pass it from a repository variable.

  • An account name in a note no longer looks like a credential. The guard now splits text at @ too, so a
    service account name such as reader@example-project-123456 passes validation.

  • The tally skill reviews every key. A new section walks an agent through coverage, missing facts, expiries
    and limits the provider offers, and stale keys, so a clean check is not mistaken for an up-to-date registry.

  • Agents can start with bare tally. Outside a terminal it prints schema JSON, including the standard parser's option definitions. Interactive terminals open the dashboard.

  • Run tally to open the dashboard. It opens at once from the tally file and fills in what the secret stores
    report when they answer, so a slow store never holds the screen. Keys nest by group, then service, and every group
    starts folded with a count of what its keys need, so an expiring key shows without opening it. A service with one
    key is that key's row. enter or → opens a group, ← folds it or goes to its parent, a filter opens every group,
    and enter on a key shows its facts and findings below the list. The dashboard uses one dark palette in every
    terminal, and a reload keeps the selected key. tally ui remains an alias.

  • Secret stores are read at once. check, notify and the dashboard list every source and look up every owner in
    parallel instead of one after another.

  • CLI options use the standard parser. Options accept --name=value, repeated locations and the -- separator.

  • A local Unix pass store is a source. pass: LABEL (optionally with a filter name prefix) lists the entries under
    PASSWORD_STORE_DIR or ~/.password-store with the modified time of each .gpg file, from directory listings only:
    nothing is decrypted or read. Names are case-sensitive, symlinks and a missing store fail the run, and init never
    drafts or links a pass entry. The date is when the ciphertext changed, not proof of rotation.

  • Google Cloud annotations carry credential facts. tally-owner, tally-service, tally-expires,
    tally-expires-note, tally-limit and tally-runbook fill an entry's unknown owner, service, expiry, limit and
    runbook. Values in .tally.yaml win, conflicting annotations fail the run, and nothing is written to the file.

  • A Google Cloud secret's expireTime is no longer a credential expiry. It is the date Secret Manager deletes the
    secret, and now raises a deletion finding within warnDays, whatever the entry's expires says.

  • Draft facts are visible. Keys drafted by tally init with service: unknown or owner: unknown now show
    unknown-service and unknown-owner gap findings.

  • Help output is predictable. Commands still print JSON when stdout is not a terminal, while help and version print
    text unless --json is given.

  • Text output is aligned. check, notify and list now show headers with aligned columns, and notifications use
    the same finding table as check output.

  • User fallback errors explain the location. Outside a repository, a missing user-level tally file now names the
    repository and gives the tally init and tally add next steps.

  • Organization owners are reported. Online checks look up owner types and report org-owner when a key cannot be
    assigned to an organization, and issue sync stops trying to assign those keys. Lookup failures are ignored, and
    validate remains a file-only offline check.

  • Assignment failures are reported and retried. Issue sync includes assignment failures in its text and JSON output,
    retries them on the next run, and continues with later writes. An edit that only retries the assignment is marked
    assign only.