AgentKit
DocsKitsCLI ReferenceDesktop App
BetaYou are reading docs for the beta channel (3.2.0-beta.10). Features may change before the next stable release.Switch to stable →

approvals

ak secrets approvals approve

Allow a pending request from another device

Use ak secrets approvals approve for the operation described below. The command help records its arguments, effects, and options.

Command contract

Allow a pending request from another device

Synopsis

Allow the pending request <id> (or a unique prefix of it) with a decision signed by this device. Without --ttl the requesting device may release the secret once; with --ttl it may release it for that long (at least 1m, at most what the request accepts, 24h by default). The command refuses to run when an agent is among its parent processes. An id that starts with "-" goes after "--", as in "ak secrets approvals approve -- -r_nM".

Effects: Signs one decision with this device's key and sends it to the vault server. The first answer wins; a request already answered, withdrawn or expired is refused with 3.

Exit status: 0 success 1 the vault server does not serve remote approvals, or an unexpected failure 2 invalid invocation, an ambiguous id prefix, or the store moved since enable 3 no pending request has that id (answered, withdrawn or expired) 5 local storage failure 6 this device may not answer (a machine device or a reader), or an agent ran approve 10 sync is not enabled on this device 11 the vault server is unavailable or busy; retry 13 integrity alarm; sync halted 14 not logged in, or this device was removed

ak secrets approvals approve <id> [flags]

Examples

  ak secrets approvals approve 3f2a
  ak secrets approvals approve 3f2a --ttl 2h --json

Options

      --backend string         Storage backend: keychain (default), file (age-encrypted vault), or memory (dev/test; values and its index are throwaway)
  -h, --help                   help for approve
      --json                   Emit machine-readable JSON (implies --no-interactive)
      --no-interactive         Disable interactive prompts (CI-safe)
  -q, --quiet                  Suppress non-error output on stderr
      --ttl string             Allow releases for this long (e.g. 30m, 2h) instead of once
      --unlock-with-recovery   Open the file backend's vault with a recovery private key and set a new passphrase
  -V, --verbose                Extra diagnostic output on stderr (loses to --quiet)
  -y, --yes                    Assume yes for all prompts

SEE ALSO